Postgresql General Discussion

• Thread Index

• Plans for ON DELETE CASCADE? Which index is used, if at all?
  • From: Dominique Devienne
• Re: Using CTID system column as a "temporary" primary key
  • From: Christophe Pettus
• Re: Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• Re: Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• Re: Using CTID system column as a "temporary" primary key
  • From: Geoff Winkless
• Re: Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• DB migration : Sybase to Postgres
  • From: Sengottaiyan T
• Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• Re: Oracle to PostgreSQL Migration
  • From: Laurenz Albe
• Re: PostgreSQL vs MariaDB
  • From: Achilleas Mantzios - cloud
• Re: PostgreSQL vs MariaDB
  • From: Thomas Guyot
• C function returning a tuple containing an array of tuples
  • From: Alberto
• Re: Binding Postgres to port 0 for testing
  • From: Markus Pilman
• Re: Binding Postgres to port 0 for testing
  • From: Markus Pilman
• Re: Binding Postgres to port 0 for testing
  • From: Michael Paquier
• Re: Binding Postgres to port 0 for testing
  • From: Michael Paquier
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Binding Postgres to port 0 for testing
  • From: Erik Wienhold
• Re: Binding Postgres to port 0 for testing
  • From: Erik Wienhold
• Re: Binding Postgres to port 0 for testing
  • From: Thorsten Glaser
• Binding Postgres to port 0 for testing
  • From: Markus Pilman
• Re: PostgreSQL vs MariaDB
  • From: Achilleas Mantzios
• Re: PostgreSQL vs MariaDB
  • From: Ron
• Re: PostgreSQL vs MariaDB
  • From: Inzamam Shafiq
• Re: psql \copy with multi-line query
  • From: Rob Sargent
• Re: psql \copy with multi-line query
  • From: David G. Johnston
• psql \copy with multi-line query
  • From: Rob Sargent
• Re: PostgreSQL vs MariaDB
  • From: Miles Elam
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Dominique Devienne
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Adrian Klaver
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Adrian Klaver
• Re: PostgreSQL vs MariaDB
  • From: Thomas Kellerer
• Re: PostgreSQL vs MariaDB
  • From: Sumit Sengupta
• Re: PostgreSQL vs MariaDB
  • From: Dominique Devienne
• Re: PostgreSQL vs MariaDB
  • From: Jeffrey Walton
• Re: PostgreSQL vs MariaDB
  • From: Ben Chobot
• Re: Oracle to PostgreSQL Migration
  • From: Christophe Pettus
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Dominique Devienne
• PostgreSQL vs MariaDB
  • From: Inzamam Shafiq
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Alvaro Herrera
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Dominique Devienne
• Re: Oracle to PostgreSQL Migration
  • From: Inzamam Shafiq
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Logical replication fails when adding multiple replicas
  • From: Will Roper
• Re: How to install vacuumlo on a client?
  • From: Adrian Klaver
• How to install vacuumlo on a client?
  • From: Zwettler Markus (OIZ)
• Re: Convert pg_constraint.conkey array to same-order array of column names
  • From: Adrian Klaver
• Re: Postgresql professional certification
  • From: Magnus Hagander
• Postgresql professional certification
  • From: MS A
• Convert pg_constraint.conkey array to same-order array of column names
  • From: Dominique Devienne
• Re: Logical replication fails when adding multiple replicas
  • From: Kyotaro Horiguchi
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Laurenz Albe
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: For temporary tables; truncate vs on commit delete all
  • From: Laurenz Albe
• For temporary tables; truncate vs on commit delete all
  • From: Jim Vanns
• Re: Logical replication fails when adding multiple replicas
  • From: Will Roper
• Re: Oracle to PostgreSQL Migration
  • From: paramjib baruah
• RE: Logical replication fails when adding multiple replicas
  • From: houzj.fnst@xxxxxxxxxxx
• Re: Is there psql cluster or replication
  • From: Ian Lawrence Barwick
• Is there psql cluster or replication
  • From: Vince McMahon
• Re: Re[2]: Getting error while upgrading postgres from version 12 to 13
  • From: Geoff Winkless
• Re: Re[2]: Getting error while upgrading postgres from version 12 to 13
  • From: Geoff Winkless
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Adrian Klaver
• Re: Oracle to PostgreSQL Migration
  • From: Marc Millas
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: shashidhar Reddy
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Adrian Klaver
• Re: Oracle to PostgreSQL Migration
  • From: Umair Shahid
• Re: Re[2]: Getting error while upgrading postgres from version 12 to 13
  • From: shashidhar Reddy
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Laurenz Albe
• Missing RHEL8 RPMS
  • From: dev dyskolos
• Re: Oracle to PostgreSQL Migration
  • From: Inzamam Shafiq
• Re: Oracle to PostgreSQL Migration
  • From: Inzamam Shafiq
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Schema/user/role
  • From: Ron Johnson
• Re: Schema/user/role
  • From: Bryn Llewellyn
• Re: Schema/user/role
  • From: David G. Johnston
• Re: Schemas and Search Path
  • From: Ron Johnson
• Re: Schemas and Search Path
  • From: Pavel Stehule
• Schema/user/role
  • From: DAVID ROTH
• Schemas and Search Path
  • From: DAVID ROTH
• Re: Oracle to PostgreSQL Migration
  • From: Jim Mlodgenski
• Re: Oracle to PostgreSQL Migration
  • From: Thomas Kellerer
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Thorsten Glaser
• Re: Oracle to PostgreSQL Migration
  • From: Ron Johnson
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: David G. Johnston
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: David G. Johnston
• Re: NULL pg_database.datacl
  • From: Dominique Devienne
• Re: NULL pg_database.datacl
  • From: Erik Wienhold
• Oracle to PostgreSQL Migration
  • From: Inzamam Shafiq
• Re: NULL pg_database.datacl
  • From: Dominique Devienne
• Logical replication fails when adding multiple replicas
  • From: Will Roper
• Re: NULL pg_database.datacl
  • From: Erik Wienhold
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• NULL pg_database.datacl
  • From: Dominique Devienne
• Re[2]: Getting error while upgrading postgres from version 12 to 13
  • From: abdulsayeed24
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: David G. Johnston
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Adrian Klaver
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: shashidhar Reddy
• Re: Properly handle OOM death?
  • From: Jeffrey Walton
• Re: Properly handle OOM death?
  • From: Tomas Pospisek
• Re: Can't connect to server
  • From: Jeff Janes
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Tomas Pospisek
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Tomas Pospisek
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: shashidhar Reddy
• Re: Getting error while upgrading postgres from version 12 to 13
  • From: Ron
• Getting error while upgrading postgres from version 12 to 13
  • From: shashidhar Reddy
• Re: Delete values from JSON
  • From: Andreas Joseph Krogh
• Re: Can't connect to server
  • From: Adrian Klaver
• Re: Delete values from JSON
  • From: Boris Zentner
• Re: Can't connect to server
  • From: Romain Mazière - SIGMAZ Consilium
• Can't connect to server
  • From: Wu, Abigaile
• Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!
  • From: Peter J. Holzer
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Peter J. Holzer
• Re: src/test/examples/testlibpq2.c where the HAVE_SYS_SELECT_H is defined.
  • From: jian he
• Re: Delete values from JSON
  • From: Andreas Joseph Krogh
• Re: nested xml/json to table
  • From: Wim Bertels
• Re: Delete values from JSON
  • From: Romain MAZIÈRE
• Re: src/test/examples/testlibpq2.c where the HAVE_SYS_SELECT_H is defined.
  • From: Thomas Munro
• Re: nested xml/json to table
  • From: Thomas Kellerer
• nested xml/json to table
  • From: Wim Bertels
• Delete values from JSON
  • From: Andreas Joseph Krogh
• src/test/examples/testlibpq2.c where the HAVE_SYS_SELECT_H is defined.
  • From: jian he
• Many logical replication synchronization worker threads kicking off for ONE table
  • From: Dolan, Sean
• Re: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!
  • From: Laurenz Albe
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Daniel Gustafsson
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Tom Lane
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• RE: EXTERNAL: Re: "No Free extents", table using all allocated space but no rows!
  • From: Dolan, Sean
• Aw: Re: Removing trailing zeros (decimal places) from a numeric (pre trim_scale()) with unexpected behaviour
  • From: magog002
• Re: valgrind a background worker
  • From: Jon Erdman
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Pavel Stehule
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Dominique Devienne
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Pavel Stehule
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Daniel Gustafsson
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Dominique Devienne
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Pavel Stehule
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Dominique Devienne
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Laurenz Albe
• Re: "No Free extents", table using all allocated space but no rows!
  • From: Laurenz Albe
• RE: uuid-ossp source or binaries for Windows
  • From: Mark Hill
• "No Free extents", table using all allocated space but no rows!
  • From: Dolan, Sean
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
  • From: Martin Goodson
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: uuid-ossp source or binaries for Windows
  • From: Daniel Gustafsson
• Re: Table scan on 15.2
  • From: Arthur Ramsey
• uuid-ossp source or binaries for Windows
  • From: Mark Hill
• Numeric Division - Result Scale Calculation Oddity
  • From: David G. Johnston
• Re: Removing trailing zeros (decimal places) from a numeric (pre trim_scale()) with unexpected behaviour
  • From: Erik Wienhold
• Re: Table scan on 15.2
  • From: Arthur Ramsey
• Re: Table scan on 15.2
  • From: Tom Lane
• Re: How to behive if I remove password from postgres role
  • From: Tom Lane
• Re: How to behive if I remove password from postgres role
  • From: Adrian Klaver
• Re: Table scan on 15.2
  • From: Arthur Ramsey
• Re: Table scan on 15.2
  • From: Tom Lane
• How to behive if I remove password from postgres role
  • From: Raivo Rebane
• Re: Table scan on 15.2
  • From: Arthur Ramsey
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• Re: Table scan on 15.2
  • From: Adrian Klaver
• Table scan on 15.2
  • From: Arthur Ramsey
• Removing trailing zeros (decimal places) from a numeric (pre trim_scale()) with unexpected behaviour
  • From: magog002
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Daniel Gustafsson
• Re: pg_upgrade Only the install user can be defined in the new cluster
  • From: Daniel Gustafsson
• pg_upgrade Only the install user can be defined in the new cluster
  • From: Dávid Suchan
• odd (maybe) procedure cacheing behaviour
  • From: Tim . Colles
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Laurenz Albe
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Adrian Klaver
• Is the PL/pgSQL refcursor useful in a modern three-tier app?
  • From: Bryn Llewellyn
• Re: Issues Scaling Postgres Concurrency
  • From: Tom Lane
• Re: Issues Scaling Postgres Concurrency
  • From: Peter J. Holzer
• Re: Issues Scaling Postgres Concurrency
  • From: Laurenz Albe
• Re: Issues Scaling Postgres Concurrency
  • From: Alan Hodgson
• Re: Issues Scaling Postgres Concurrency
  • From: Adrian Klaver
• Issues Scaling Postgres Concurrency
  • From: Harrison Borges
• Re: Problems connecting to the server
  • From: Adrian Klaver
• Problems connecting to the server
  • From: Arsen Deputat
• Re: Seq Scan because of stats or because of cast?
  • From: Dominique Devienne
• Re: Uppercase version of ß desired
  • From: Celia McInnis
• Re: Uppercase version of ß desired
  • From: Kip Cole
• Re: Uppercase version of ß desired
  • From: Philip Semanchuk
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: David Rowley
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: David Rowley
• Re: Uppercase version of ß desired
  • From: Thorsten Glaser
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: Alban Hertroys
• Re: Seq Scan because of stats or because of cast?
  • From: Dominique Devienne
• Re: Uppercase version of ß desired
  • From: Celia McInnis
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: Ben Clements
• Re: Uppercase version of ß desired
  • From: Tom Lane
• Re: Uppercase version of ß desired
  • From: Peter J. Holzer
• Using GSSAPI/Kerbros/Active Directory: want the database user name to be the full name including the realm name without specifying the user
  • From: Michael Downey
• Uppercase version of ß desired
  • From: Celia McInnis
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Peter J. Holzer
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Properly handle OOM death?
  • From: Jeffrey Walton
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Binary large object processing problems
  • From: Raivo Rebane
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Peter J. Holzer
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Israel Brewster
• Re: Properly handle OOM death?
  • From: Joe Conway
• Re: Properly handle OOM death?
  • From: Adrian Klaver
• Properly handle OOM death?
  • From: Israel Brewster
• Re: Binary large object processing problems
  • From: Tom Lane
• Re: Binary large object processing problems
  • From: Raivo Rebane
• Re: Binary large object processing problems
  • From: Christoph Moench-Tegeder
• Binary large object processing problems
  • From: Raivo Rebane
• Re: Seq Scan because of stats or because of cast?
  • From: Tom Lane
• Seq Scan because of stats or because of cast?
  • From: Dominique Devienne
• Re: can't get psql authentication against Active Directory working
  • From: Stephen Frost
• Re: Practice advice for use of %type in declaring a subprogram's formal arguments
  • From: Bryn Llewellyn
• Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
  • From: Adrian Klaver
• Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
  • From: Martin Goodson
• Re: Help? Unexpected PostgreSQL compilation failure using generic compile script
  • From: Tom Lane
• Help? Unexpected PostgreSQL compilation failure using generic compile script
  • From: Martin Goodson
• Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  • From: Laurenz Albe
• Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  • From: Ron
• Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  • From: Laurenz Albe
• Re: ERROR: only immutable functions supported in continuous aggregate view
  • From: Martijn de Munnik
• Re: Idea: Add first() and last() aggregate functions to the main release
  • From: Erwin Brandstetter
• Re: confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  • From: Ron
• confusion between max_standby_archive_delay, max_standby_archive_delay and max_standby_archive_delay
  • From: Atul Kumar
• Re: ERROR: only immutable functions supported in continuous aggregate view
  • From: Tom Lane
• ERROR: only immutable functions supported in continuous aggregate view
  • From: Martijn de Munnik
• Idea: Add first() and last() aggregate functions to the main release
  • From: Ben Clements
• Re: Practice advice for use of %type in declaring a subprogram's formal arguments
  • From: Ron
• Re: Practice advice for use of %type in declaring a subprogram's formal arguments
  • From: David G. Johnston
• Practice advice for use of %type in declaring a subprogram's formal arguments
  • From: Bryn Llewellyn
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: David G. Johnston
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: Bryn Llewellyn
• Re: can't get psql authentication against Active Directory working
  • From: Tomas Pospisek
• Re: Get more columns from a lookup type subselect
  • From: negora
• Re: Get more columns from a lookup type subselect
  • From: Durumdara
• Re: Get more columns from a lookup type subselect
  • From: negora
• SV: Onfly, function generated ID for Select Query
  • From: Gustavsson Mikael
• Re: Onfly, function generated ID for Select Query
  • From: Durumdara
• Get more columns from a lookup type subselect
  • From: Durumdara
• SV: Onfly, function generated ID for Select Query
  • From: Gustavsson Mikael
• Onfly, function generated ID for Select Query
  • From: Durumdara
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: David G. Johnston
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: Bryn Llewellyn
• Re: public schema grants to PUBLIC role
  • From: Dominique Devienne
• find coumn name and his type with greatest size in bytes
  • From: Алексей Ефимов
• Re: crosstab
  • From: David G. Johnston
• Re: public schema grants to PUBLIC role
  • From: Laurenz Albe
• crosstab
  • From: Rosebrock, Uwe (Environment, Hobart)
• RE: Blog post series on commitfests and patches
  • From: Tim Clarke
• Re: public schema grants to PUBLIC role
  • From: Christoph Moench-Tegeder
• public schema grants to PUBLIC role
  • From: Dominique Devienne
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Pavel Stehule
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: David G. Johnston
• Blog post series on commitfests and patches
  • From: Chris Travers
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: Bryn Llewellyn
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: Tom Lane
• Re: select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: David G. Johnston
• select (17, 42)::s.t2 into... fails with "invalid input syntax"
  • From: Bryn Llewellyn
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Ron
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Bryn Llewellyn
• Re: could not bind IPv4 address "127.0.0.1": Address already in use
  • From: Siddharth Jain
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Bryn Llewellyn
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Tom Lane
• Re: could not bind IPv4 address "127.0.0.1": Address already in use
  • From: Tom Lane
• Fwd: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• could not bind IPv4 address "127.0.0.1": Address already in use
  • From: Siddharth Jain
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Bryn Llewellyn
• Re: Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: David G. Johnston
• Behavior of PL/pgSQL function following drop and re-create of a table that it uses
  • From: Bryn Llewellyn
• Re: garbage data back
  • From: Brad White
• Re: psql \conninfo in tabular form?
  • From: Erik Wienhold
• psql \conninfo in tabular form?
  • From: Ron
• Re: escape vs. bytea in config
  • From: Peter J. Holzer
• Re: escape vs. bytea in config
  • From: Laurenz Albe
• Re: Multiple core dump errors are thrown by initdb when Huge pages are enabled in OS and huge_pages is set to “off” in postgresql.conf.sample in Kubernetes.
  • From: Julien Rouhaud
• Multiple core dump errors are thrown by initdb when Huge pages are enabled in OS and huge_pages is set to “off” in postgresql.conf.sample in Kubernetes.
  • From: M Tarkeshwar Rao
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: David Rowley
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: David G. Johnston
• Re: How does Postgres store a B-Tree on disk while using the OS file system?
  • From: Siddharth Jain
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: David Rowley
• Re: How does Postgres store a B-Tree on disk while using the OS file system?
  • From: Christophe Pettus
• Re: How does Postgres store a B-Tree on disk while using the OS file system?
  • From: Ron
• How does Postgres store a B-Tree on disk while using the OS file system?
  • From: Siddharth Jain
• Re: Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: Tom Lane
• Idea: PostgreSQL equivalent to Oracle's KEEP clause
  • From: Ben Clements
• Re: garbage data back
  • From: Adrian Klaver
• Re: garbage data back
  • From: Brad White
• Re: Fwd: garbage data back
  • From: Adrian Klaver
• Re: garbage data back
  • From: David G. Johnston
• Fwd: garbage data back
  • From: Brad White
• Re: garbage data back
  • From: David G. Johnston
• Re: garbage data back
  • From: Adrian Klaver
• garbage data back
  • From: Brad White
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Dominique Devienne
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Dominique Devienne
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Tom Lane
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Dominique Devienne
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Tom Lane
• Re: CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Erik Wienhold
• CREATE/DROP ROLE transactional? GRANT/REVOKE?
  • From: Dominique Devienne
• Re: Row Level Security Policy Name in Error Message
  • From: Daniel Gustafsson
• Row Level Security Policy Name in Error Message
  • From: Louis Tian
• Re: what's hsitoric MVCC Snapshot?
  • From: Adrian Klaver
• Re: what's hsitoric MVCC Snapshot?
  • From: Adrian Klaver
• what's hsitoric MVCC Snapshot?
  • From: jacktby@xxxxxxxxx
• Re: psql \set variables in crosstab queries?
  • From: David G. Johnston
• Re: psql \set variables in crosstab queries?
  • From: Ron
• Re: psql \set variables in crosstab queries?
  • From: Ron
• Re: psql \set variables in crosstab queries?
  • From: David G. Johnston
• Re: psql \set variables in crosstab queries?
  • From: Tom Lane
• psql \set variables in crosstab queries?
  • From: Ron
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Ron
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Thorsten Glaser
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Conner Bean
• Re: shp2pgsql error under windows
  • From: Christoph Moench-Tegeder
• shp2pgsql error under windows
  • From: Raivo Rebane
• shp2pgsql generates fake fail full of zeroes
  • From: Raivo Rebane
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Peter J. Holzer
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Alban Hertroys
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Ron
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Peter J. Holzer
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Peter J. Holzer
• Re: Converting row elements into a arrays?
  • From: Pavel Stehule
• Re: Dropping behavior for unique CONSTRAINTs
  • From: David Rowley
• Re: 13.x, stream replication and locale(?) issues
  • From: Thomas Munro
• Re: Dropping behavior for unique CONSTRAINTs
  • From: Ron
• Re: Converting row elements into a arrays?
  • From: Merlin Moncure
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Thorsten Glaser
• Re: PG16devel - vacuum_freeze_table_age seems not being taken into account
  • From: Peter Geoghegan
• Re: PG16devel - vacuum_freeze_table_age seems not being taken into account
  • From: Simon Elbaz
• Re: PG16devel - vacuum_freeze_table_age seems not being taken into account
  • From: David Rowley
• Re: Dropping behavior for unique CONSTRAINTs
  • From: David Rowley
• PG16devel - vacuum_freeze_table_age seems not being taken into account
  • From: Simon Elbaz
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: David Rowley
• Dropping behavior for unique CONSTRAINTs
  • From: Conner Bean
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: cen
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Alban Hertroys
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: David Rowley
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: Kirk Wolak
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Thorsten Glaser
• Re: Converting row elements into a arrays?
  • From: Rob Sargent
• Re: Converting row elements into a arrays?
  • From: Ron
• Re: Converting row elements into a arrays?
  • From: Ron
• Re: Converting row elements into a arrays?
  • From: Ron
• Re: Converting row elements into a arrays?
  • From: Rob Sargent
• Re: Converting row elements into a arrays?
  • From: David G. Johnston
• Re: Converting row elements into a arrays?
  • From: Ray O'Donnell
• Re: Converting row elements into a arrays?
  • From: Ray O'Donnell
• Converting row elements into a arrays?
  • From: Ron
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: cen
• Re: Getting the exact SQL from inside an event trigger
  • From: Joe Wildish
• Re: Getting the exact SQL from inside an event trigger
  • From: hubert depesz lubaczewski
• Getting the exact SQL from inside an event trigger
  • From: Joe Wildish
• Re: Postgres Index and Updates
  • From: Dominique Devienne
• Re: Postgres Index and Updates
  • From: Laurenz Albe
• Re: Failed upgrade from 12.11 to 14.4
  • From: Arthur Ramsey
• Postgres Index and Updates
  • From: Navindren Baskaran
• Re: Failed upgrade from 12.11 to 14.4
  • From: Tom Lane
• Failed upgrade from 12.11 to 14.4
  • From: Arthur Ramsey
• Re: Interval in hours but not in days Leap second not taken into account
  • From: Thomas Munro
• Re: 13.x, stream replication and locale(?) issues
  • From: Thomas Munro
• Re: Quit currently running query
  • From: Ron
• Re: Quit currently running query
  • From: Peter J. Holzer
• Re: Move all elements toward another schema?
  • From: Marcos Pegoraro
• Re: Move all elements toward another schema?
  • From: David G. Johnston
• Move all elements toward another schema?
  • From: celati Laurent
• Re: Quit currently running query
  • From: Rob Sargent
• Re: 13.x, stream replication and locale(?) issues
  • From: Tom Lane
• Re: Quit currently running query
  • From: Ron
• Re: Quit currently running query
  • From: Ian Lawrence Barwick
• Quit currently running query
  • From: Albert Cornelius
• 13.x, stream replication and locale(?) issues
  • From: Eugene M. Zheganin
• Re: Tempory table is not getting created inside Function in postgres.
  • From: nikhil raj
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Alban Hertroys
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)y
  • From: Thorsten Glaser
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: David G. Johnston
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: Tom Lane
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: Thorsten Glaser
• Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Jan Bilek
• Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Jan Bilek
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: David G. Johnston
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: David G. Johnston
• Re: DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: Tom Lane
• DISTINCT *and* ORDER BY in aggregate functions on expressions(!)
  • From: mirabilos
• Re: pg_get_functiondef(), trailing spaces and + sign
  • From: Kirk Wolak
• Re: Tempory table is not getting created inside Function in postgres.
  • From: David G. Johnston
• Re: Tempory table is not getting created inside Function in postgres.
  • From: nikhil raj
• Re: Tempory table is not getting created inside Function in postgres.
  • From: Tom Lane
• Re: Tempory table is not getting created inside Function in postgres.
  • From: Adrian Klaver
• Re: Tempory table is not getting created inside Function in postgres.
  • From: Adrian Klaver
• Re: pg_get_functiondef(), trailing spaces and + sign
  • From: Adrian Klaver
• Re: pg_get_functiondef(), trailing spaces and + sign
  • From: Adrian Klaver
• pg_get_functiondef(), trailing spaces and + sign
  • From: Ron
• Tempory table is not getting created inside Function in postgres.
  • From: nikhil raj
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Dávid Suchan
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Dávid Suchan
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Laurenz Albe
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Dávid Suchan
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Tom Lane
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Tom Lane
• Re: pg_upgradecluster transfering only a portion of the data
  • From: Adrian Klaver
• Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Tom Lane
• pg_upgradecluster transfering only a portion of the data
  • From: Dávid Suchan
• Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Erik Wienhold
• Re: Repear operations on 50 tables of the same schema?
  • From: Ron
• Re: Event Triggers unable to capture the DDL script executed
  • From: Laurenz Albe
• Re: ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Laurenz Albe
• Repear operations on 50 tables of the same schema?
  • From: celati Laurent
• Re: Interval in hours but not in days Leap second not taken into account
  • From: PALAYRET Jacques
• Re: Interval in hours but not in days Leap second not taken into account
  • From: PALAYRET Jacques
• Re: Interval in hours but not in days Leap second not taken into account
  • From: Laurenz Albe
• Interval in hours but not in days Leap second not taken into account
  • From: PALAYRET Jacques
• ERROR: unsupported Unicode escape sequence - in JSON-type column
  • From: Jan Bilek
• Re: Event Triggers unable to capture the DDL script executed
  • From: Neethu P
• Re: Give me details of some attributes!!
  • From: Laurenz Albe
• Comparing Postgres logical replication to MySQL
  • From: Siddharth Jain
• Give me details of some attributes!!
  • From: jacktby@xxxxxxxxx
• Re: IS as a binary operator
  • From: Tom Lane
• IS as a binary operator
  • From: david wheeler
• Re: can't get psql authentication against Active Directory working
  • From: Stephen Frost
• Re: curiosity in default column header
  • From: David G. Johnston
• curiosity in default column header
  • From: Rob Sargent
• Re: Debugging postgres on Windows - could not open directory "/lib"
  • From: Adrian Klaver
• Re: PostgreSQL optimizations for CoW FS
  • From: Peter Eisentraut
• Re: can't get psql authentication against Active Directory working
  • From: Tomas Pospisek
• Re: Debugging postgres on Windows - could not open directory "/lib"
  • From: Cathy Xie
• Re: RLS without leakproof restrictions?
  • From: Stephen Frost
• Re: Event Triggers unable to capture the DDL script executed
  • From: Neethu P
• Re: Event Triggers unable to capture the DDL script executed
  • From: Laurenz Albe
• Re: Event Triggers unable to capture the DDL script executed
  • From: Neethu P
• Re: Debugging postgres on Windows - could not open directory "/lib"
  • From: Adrian Klaver
• Re: Memory leak using when using libpq PQExecParams() CRYPTO_zalloc()
  • From: Jeffrey Walton
• Memory leak using when using libpq PQExecParams() CRYPTO_zalloc()
  • From: Michael Arnold
• RE: Event Triggers unable to capture the DDL script executed
  • From: n.kobzarev
• Re: Event Triggers unable to capture the DDL script executed
  • From: Laurenz Albe
• PostgreSQL optimizations for CoW FS
  • From: HECTOR INGERTO
• Event Triggers unable to capture the DDL script executed
  • From: Neethu P
• Re: Debugging postgres on Windows - could not open directory "/lib"
  • From: Cathy Xie
• Re: RLS without leakproof restrictions?
  • From: Tom Dunstan
• Re: RLS without leakproof restrictions?
  • From: Tom Lane
• Re: RLS without leakproof restrictions?
  • From: Tom Dunstan
• Re: RLS without leakproof restrictions?
  • From: Martin L. Buchanan
• RLS without leakproof restrictions?
  • From: Tom Dunstan
• Re: transaction_isolation vs. default_transaction_isolation
  • From: Bryn Llewellyn
• Re: Is Autovacuum running?
  • From: David Rowley
• Re: Debugging postgres on Windows - could not open directory "/lib"
  • From: Adrian Klaver
• Debugging postgres on Windows - could not open directory "/lib"
  • From: Cathy Xie
• Re: Is Autovacuum running?
  • From: Brad White
• Re: Is Autovacuum running?
  • From: David Rowley
• Re: transaction_isolation vs. default_transaction_isolation
  • From: David G. Johnston
• Re: Is Autovacuum running?
  • From: Christophe Pettus
• transaction_isolation vs. default_transaction_isolation
  • From: Bryn Llewellyn
• Re: Is Autovacuum running?
  • From: Brad White
• Re: Is Autovacuum running?
  • From: Christophe Pettus
• Re: Is Autovacuum running?
  • From: Brad White
• Re: can't get psql authentication against Active Directory working
  • From: Stephen Frost
• Re: Hi All,
  • From: Tom Lane
• Re: can't get psql authentication against Active Directory working
  • From: Tomas Pospisek
• Re:
  • From: Carsten Klein
• [no subject]
  • From: Alberto García Fumero
• Aw: Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Karsten Hilbert
• Re: Sequential scan faster than index
  • From: David Rowley
• Re: Sequential scan faster than index
  • From: Luca Ferrari
• Please upload patroni 3.0.1 package to postgresql repo
  • From: SUN YI
• Need Detailed to build real time CDC Data Pipeline
  • From: Puja Anil AJMERA
• Hi All,
  • From: Ryan MYJ
• Sequential scan faster than index
  • From: Arthur Ramsey
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Peter Geoghegan
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Mikhail Balayan
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: Adrian Klaver
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: pf
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Bryn Llewellyn
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Christophe Pettus
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Bryn Llewellyn
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: Adrian Klaver
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Daniel Verite
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Bryn Llewellyn
• Re: pg_reload_conf()
  • From: Marc Millas
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: David G. Johnston
• Re: Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Christophe Pettus
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: Adrian Klaver
• Thanks! Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Bryn Llewellyn
• Is Autovacuum running?
  • From: Brad White
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: pf
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: Adrian Klaver
• Re: pg_dump'ed file contains "DROP DATABASE"
  • From: Tom Lane
• pg_dump'ed file contains "DROP DATABASE"
  • From: pf
• Re: pg_reload_conf()
  • From: David G. Johnston
• Re: pg_reload_conf()
  • From: Adrian Klaver
• pg_reload_conf()
  • From: Marc Millas
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Kirk Wolak
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Tom Lane
• Re: can't get psql authentication against Active Directory working
  • From: Stephen Frost
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: David Rowley
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Mikhail Balayan
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Pavel Stehule
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Tom Lane
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: David Rowley
• Re: A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Tom Lane
• A performance issue in ROW_NUMBER() OVER(ORDER BY NULL) [27 times slow than OVER()] V14.5
  • From: Kirk Wolak
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Christophe Pettus
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Ian Lawrence Barwick
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: David G. Johnston
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Christophe Pettus
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Christophe Pettus
• Re: Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Julien Rouhaud
• Who adds the "start transaction" and "commit" to the intended SQL statement in "autocommit" mode?
  • From: Bryn Llewellyn
• Re: Does Postgres 14 have a query cache?
  • From: Tatsuo Ishii
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Mikhail Balayan
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Mikhail Balayan
• Re: Does Postgres 14 have a query cache?
  • From: Siddharth Jain
• Re: Does Postgres 14 have a query cache?
  • From: Steven Lembark
• Re: Does Postgres 14 have a query cache?
  • From: Ron
• Re: can't get psql authentication against Active Directory working
  • From: Tomas Pospisek
• Re: can't get psql authentication against Active Directory working
  • From: Erik Wienhold
• Re: Does Postgres 14 have a query cache?
  • From: Christophe Pettus
• Re: Does Postgres 14 have a query cache?
  • From: Peter J. Holzer
• Re: Does Postgres 14 have a query cache?
  • From: David G. Johnston
• Does Postgres 14 have a query cache?
  • From: Siddharth Jain
• can't get psql authentication against Active Directory working
  • From: Tomas Pospisek
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Peter Geoghegan
• Re: Query plan for "id IS NULL" on PK
  • From: Ben Chrobot
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: Marc Millas
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: cen
• Sv: PostgreSQL configuration in a VM
  • From: Andreas Joseph Krogh
• PostgreSQL configuration in a VM
  • From: Sebastien Flaesch
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: Ken Tanzer
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: Adrian Klaver
• Re: DELETE trigger, direct or indirect?
  • From: Adrian Klaver
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: David Wheeler
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Peter Geoghegan
• Re: Vacuum full issue
  • From: Adrian Klaver
• Re: Vacuum full issue
  • From: David G. Johnston
• Vacuum full issue
  • From: Rama Krishnan
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: David G. Johnston
• Re: DELETE trigger, direct or indirect?
  • From: Brad White
• Re: DELETE trigger, direct or indirect?
  • From: Dominique Devienne
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: Dominique Devienne
• Re: How to avoid Trigger ping/pong / infinite loop
  • From: Adrian Klaver
• Re: DELETE trigger, direct or indirect?
  • From: Adrian Klaver
• How to avoid Trigger ping/pong / infinite loop
  • From: Dominique Devienne
• Re: DELETE trigger, direct or indirect?
  • From: Dominique Devienne
• Re: DELETE trigger, direct or indirect?
  • From: Adrian Klaver
• Re: DELETE trigger, direct or indirect?
  • From: David G. Johnston
• Re: DELETE trigger, direct or indirect?
  • From: Adrian Klaver
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: Ron
• Re: DELETE trigger, direct or indirect?
  • From: Erik Wienhold
• Re: Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: David G. Johnston
• Postgres undeterministically uses a bad plan, how to convince it otherwise?
  • From: cen
• Re: Automatic aggressive vacuum on almost frozen table takes too long
  • From: Adrian Klaver
• DELETE trigger, direct or indirect?
  • From: Dominique Devienne
• Automatic aggressive vacuum on almost frozen table takes too long
  • From: Mikhail Balayan
• Re: Multi-column index: Which column order
  • From: Laurenz Albe
• Aggressive vacuum frequency on a table
  • From: Simon Elbaz
• Re: Multi-column index: Which column order
  • From: Ron
• Re: Multi-column index: Which column order
  • From: Laurenz Albe
• Re: Multi-column index: Which column order
  • From: Ron
• Re: Query plan for "id IS NULL" on PK
  • From: Ron
• Re: unresolved external symbol when building on Windows
  • From: Andy Y
• unresolved external symbol when building on Windows
  • From: King of Hearts
• Re: Multi-column index: Which column order
  • From: Laurenz Albe
• Re: Order of rows in simple "select r from table_fn()"
  • From: Bryn Llewellyn
• Re: Order of rows in simple "select r from table_fn()"
  • From: Pavel Stehule
• Re: Query plan for "id IS NULL" on PK
  • From: Tom Lane
• Re: Quoting issue from ODBC
  • From: Adrian Klaver
• Re: Query plan for "id IS NULL" on PK
  • From: David Rowley
• Re: Order of rows in simple "select r from table_fn()"
  • From: David G. Johnston
• Order of rows in simple "select r from table_fn()"
  • From: Bryn Llewellyn
• Re: Quoting issue from ODBC
  • From: Brad White
• Re: Query plan for "id IS NULL" on PK
  • From: Rob Sargent
• Re: Query plan for "id IS NULL" on PK
  • From: Peter J. Holzer
• Re: Query plan for "id IS NULL" on PK
  • From: Peter J. Holzer
• Re: Query plan for "id IS NULL" on PK
  • From: Rob Sargent
• Re: Query plan for "id IS NULL" on PK
  • From: David G. Johnston
• Re: Query plan for "id IS NULL" on PK
  • From: Rob Sargent
• Query plan for "id IS NULL" on PK
  • From: Ben Chrobot
• pro services list
  • From: Rob Sargent
• Re: Multi-column index: Which column order
  • From: Erik Wienhold
• [Outcome] Queries running forever, because of wrong rowcount estimate
  • From: Peter
• Multi-column index: Which column order
  • From: Sebastien Flaesch
• Re: Losing my latin on Ordering...
  • From: Laurenz Albe
• Re: Losing my latin on Ordering...
  • From: Dominique Devienne
• Re: Losing my latin on Ordering...
  • From: Laurenz Albe
• Re: Losing my latin on Ordering...
  • From: Alvaro Herrera
• Re: Losing my latin on Ordering...
  • From: Dominique Devienne
• Re: Losing my latin on Ordering...
  • From: Laurenz Albe
• Losing my latin on Ordering...
  • From: Dominique Devienne
• Re: HOWTO? Permissions for user to access a single db
  • From: Rob Sargent
• Re: HOWTO? Permissions for user to access a single db
  • From: Damian Carey
• Re: HOWTO? Permissions for user to access a single db
  • From: Adrian Klaver
• Re: HOWTO? Permissions for user to access a single db
  • From: Tom Lane
• Re: HOWTO? Permissions for user to access a single db
  • From: Rob Sargent
• Re: HOWTO? Permissions for user to access a single db
  • From: Damian Carey
• Re: HOWTO? Permissions for user to access a single db
  • From: Tom Lane
• Re: HOWTO? Permissions for user to access a single db
  • From: Damian Carey
• Re: HOWTO? Permissions for user to access a single db
  • From: Tom Lane
• HOWTO? Permissions for user to access a single db
  • From: Damian Carey
• Re: [Testcase] Queries running forever, because of wrong rowcount estimate
  • From: Peter
• Re: [Testcase] Queries running forever, because of wrong rowcount estimate
  • From: Tom Lane
• [Testcase] Queries running forever, because of wrong rowcount estimate
  • From: Peter
• Re: pg_dump problem with postgres user
  • From: Adrian Klaver
• Re: pg_dump problem with postgres user
  • From: ertan.kucukoglu
• Re: psql "\d" no longer working
  • From: Rob Sargent
• Re: psql "\d" no longer working
  • From: Adrian Klaver
• Re: psql "\d" no longer working
  • From: Ron
• Re: psql "\d" no longer working
  • From: Adrian Klaver
• Re: pg_dump problem with postgres user
  • From: David G. Johnston
• pg_dump problem with postgres user
  • From: ertan.kucukoglu
• Re: psql "\d" no longer working
  • From: Georg H.
• psql "\d" no longer working
  • From: Rob Sargent
• Queries running forever, because of wrong rowcount estimate
  • From: Peter
• Re: pg_trgm vs. Solr ngram
  • From: Christian Ramseyer (mx04)
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Peter J. Holzer
• Re: valgrind a background worker
  • From: Jon Erdman
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Peter J. Holzer
• Re: How to pass table column values to function
  • From: jian he
• Re: How to pass table column values to function
  • From: Marcos Pegoraro
• How to pass table column values to function
  • From: Andrus
• Re: valgrind a background worker
  • From: Tom Lane
• Re: valgrind a background worker
  • From: Jeffrey Walton
• Re: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Adrian Klaver
• Re: valgrind a background worker
  • From: Tom Lane
• RE: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Lawrence, Mike (DTST)
• Re: valgrind a background worker
  • From: Jon Erdman
• Re: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Adrian Klaver
• RE: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Lawrence, Mike (DTST)
• Re: PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Adrian Klaver
• PostgreSQL 13.9.3 Uninstall fails with "Unable to initialize any installation mode"
  • From: Lawrence, Mike (DTST)
• Re: valgrind a background worker
  • From: Tom Lane
• Re: How to use the BRIN index properly?
  • From: GF
• valgrind a background worker
  • From: Jon Erdman
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Alban Hertroys
• Re: pg_trgm vs. Solr ngram
  • From: Bertrand Mamasam
• Re: pg_trgm vs. Solr ngram
  • From: Tom Lane
• Re: pg_trgm vs. Solr ngram
  • From: Laurenz Albe
• pg_trgm vs. Solr ngram
  • From: Chris
• Re: ERROR: posting list tuple with 2 items cannot be split at offset 17
  • From: Peter Geoghegan
• Re: Quoting issue from ODBC
  • From: Brad White
• Re: ERROR: posting list tuple with 2 items cannot be split at offset 17
  • From: Paul McGarry
• Re: Quoting issue from ODBC
  • From: Adrian Klaver
• Re: Quoting issue from ODBC
  • From: Brad White
• Re: Quoting issue from ODBC
  • From: Brad White
• Re: Concurrency issue with DROP INDEX CONCURRENTLY
  • From: Laurenz Albe
• Re: Concurrency issue with DROP INDEX CONCURRENTLY
  • From: Kiriakos Georgiou
• delta.io foreign data wrapper
  • From: Georg Heiler
• Re: Using PostgreSQL for service discovery and health-check
  • From: Adrian Klaver
• Re: Sequence vs UUID
  • From: Merlin Moncure
• Re: Using PostgreSQL for service discovery and health-check
  • From: Adrian Klaver
• Re: Using PostgreSQL for service discovery and health-check
  • From: Dominique Devienne
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Dominique Devienne
• Re: ERROR: posting list tuple with 2 items cannot be split at offset 17
  • From: Peter Geoghegan
• Re: ERROR: posting list tuple with 2 items cannot be split at offset 17
  • From: Adrian Klaver
• Re: Using PostgreSQL for service discovery and health-check
  • From: Adrian Klaver
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: David G. Johnston
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Alban Hertroys
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: David G. Johnston
• Re: Using PostgreSQL for service discovery and health-check
  • From: Dominique Devienne
• Re: Concurrency issue with DROP INDEX CONCURRENTLY
  • From: Adrian Klaver
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Dominique Devienne
• Re: Using PostgreSQL for service discovery and health-check
  • From: Adrian Klaver
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: Dominique Devienne
• Re: Using PostgreSQL for service discovery and health-check
  • From: Dominique Devienne
• Re: WHERE col = ANY($1) extended to 2 or more columns?
  • From: David G. Johnston
• Re: Using PostgreSQL for service discovery and health-check
  • From: David G. Johnston
• Concurrency issue with DROP INDEX CONCURRENTLY
  • From: Kiriakos Georgiou
• Re: PostgreSQL
  • From: Laurenz Albe
• WHERE col = ANY($1) extended to 2 or more columns?
  • From: Dominique Devienne
• Using PostgreSQL for service discovery and health-check
  • From: Dominique Devienne
• Re: Question regarding UTF-8 data and "C" collation on definition of field of table
  • From: Jehan-Guillaume de Rorthais
• Re: PostgreSQL
  • From: Joseph Kennedy
• ERROR: posting list tuple with 2 items cannot be split at offset 17
  • From: Paul McGarry
• Re: Boyer-Moore string searching in LIKE, ILIKE, and/or POSITION?
  • From: Vladimir Sitnikov
• Re: Boyer-Moore string searching in LIKE, ILIKE, and/or POSITION?
  • From: David Rowley
• Re: Boyer-Moore string searching in LIKE, ILIKE, and/or POSITION?
  • From: Tom Lane
• Re: Boyer-Moore string searching in LIKE, ILIKE, and/or POSITION?
  • From: David Rowley
• Boyer-Moore string searching in LIKE, ILIKE, and/or POSITION?
  • From: Martin L. Buchanan
• Re: How do a user-defined function that returns a table executes a query?
  • From: Katsuya Okizaki
• Re: How to create directory format backup
  • From: Tom Lane
• Re: How do a user-defined function that returns a table executes a query?
  • From: Katsuya Okizaki
• Re: How to create directory format backup
  • From: Erik Wienhold
• Re: How to use the BRIN index properly?
  • From: Ron
• Re: How to use the BRIN index properly?
  • From: Christophe Pettus
• Re: How to use the BRIN index properly?
  • From: Siddharth Jain
• Re: How to create directory format backup
  • From: Andrus
• Re: How to use the BRIN index properly?
  • From: Christophe Pettus
• Re: How to create directory format backup
  • From: Erik Wienhold
• Re: How to use the BRIN index properly?
  • From: Siddharth Jain
• Re: How to create directory format backup
  • From: Andrus
• Re: Sequence vs UUID
  • From: Miles Elam
• Re: How to use the BRIN index properly?
  • From: Ron
• Re: How to use the BRIN index properly?
  • From: Siddharth Jain
• Re: Sequence vs UUID
  • From: Kirk Wolak
• How to use the BRIN index properly?
  • From: Siddharth Jain
• How to verify postrgresql download on windows?
  • From: Ali M.
• Re: How to create directory format backup
  • From: hubert depesz lubaczewski
• Re: Need help debugging slow logical replication
  • From: sunyucong@xxxxxxxxx
• How to create directory format backup
  • From: Andrus
• Re: Index scan for PK constraint validation
  • From: David G. Johnston
• Re: Get the sequence name corresponding to a GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY column
  • From: Sebastien Flaesch
• Index scan for PK constraint validation
  • From: Philippe VIEGAS
• Re: Sequence vs UUID
  • From: Peter J. Holzer
• Re: Get the sequence name corresponding to a GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY column
  • From: Peter Eisentraut
• Re: Switching identity column to serial
  • From: Peter Eisentraut
• Re: How do a user-defined function that returns a table executes a query?
  • From: Laurenz Albe
• Re: Sequence vs UUID
  • From: veem v
• Re: Need help debugging slow logical replication
  • From: sunyucong@xxxxxxxxx
• Re: Quoting issue from ODBC
  • From: Brad White
• Re: Need help debugging slow logical replication
  • From: sunyucong@xxxxxxxxx
• Re: Need help debugging slow logical replication
  • From: Justin
• Re: Need help debugging slow logical replication
  • From: sunyucong@xxxxxxxxx
• Re: PostgreSQL
  • From: Stephen Frost
• Re: Quoting issue from ODBC
  • From: Rob Sargent
• Re: Quoting issue from ODBC
  • From: David G. Johnston
• Fwd: Quoting issue from ODBC
  • From: Brad White
• Re: Need help debugging slow logical replication
  • From: Justin
• Re: Quoting issue from ODBC
  • From: Adrian Klaver
• Opportunity for clarification on ODBC options
  • From: Brad White
• Re: A Small psql Suggestion
  • From: Brad White
• Re: PostgreSQL
  • From: Brad White
• Quoting issue from ODBC
  • From: Brad White
• Re: A Small psql Suggestion
  • From: Adrian Klaver
• Re: A Small psql Suggestion
  • From: Brad White
• Re: How do a user-defined function that returns a table executes a query?
  • From: David G. Johnston
• How do a user-defined function that returns a table executes a query?
  • From: Katsuya Okizaki
• Re: PostgreSQL
  • From: Brad White
• Need help debugging slow logical replication
  • From: sunyucong@xxxxxxxxx
• Re: PostgreSQL
  • From: Peter J. Holzer
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Ron
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Ron
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Tom Lane
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Laurenz Albe
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Ron
• Re: A Small psql Suggestion
  • From: Raymond Brinzer
• Re: Sequence vs UUID
  • From: Dominique Devienne
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Adrian Klaver
• Re: Sequence vs UUID
  • From: Merlin Moncure
• Re: PostgreSQL
  • From: Joseph Kennedy
• Re: ERROR: deadlock detected
  • From: Laurenz Albe
• Re: PostgreSQL
  • From: Laurenz Albe
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Philip Semanchuk
• Re: PostgreSQL
  • From: Giovanni Biscontini
• Re: ERROR: deadlock detected
  • From: Torsten Förtsch
• ERROR: deadlock detected
  • From: Matthias Apitz
• Re: PostgreSQL
  • From: Joseph Kennedy
• Re: PostgreSQL
  • From: Giovanni Biscontini
• Re: PostgreSQL
  • From: Thomas Kellerer
• Re: Too coarse predicate locks granularity for B+ tree indexes
  • From: Rinat Shigapov
• PostgreSQL
  • From: Joseph Kennedy
• Re: Get the sequence name corresponding to a GENERATED { ALWAYS | BY DEFAULT } AS IDENTITY column
  • From: Sebastien Flaesch
• Re: Too coarse predicate locks granularity for B+ tree indexes
  • From: Laurenz Albe
• Re: Logical Replication - "invalid ordering of speculative insertion changes"
  • From: Rahila Syed
• Re: ALTER COLUMN to change GENERATED ALWAYS AS expression?
  • From: Laurenz Albe
• Re: Language options for GIN index support functions
  • From: Pavel Stehule