Postgresql General Discussion

• Thread Index

• Re: Multiple Postgrest Verisons how to set one version as default.
  • From: Ron
• Multiple Postgrest Verisons how to set one version as default.
  • From: Gautham Raj
• Re: HOT update: why must ALL indexes should be update?
  • From: Bruce Momjian
• Re: PostgreSQL in-transit compression for a client connection
  • From: Dominique Devienne
• Re: PostgreSQL in-transit compression for a client connection
  • From: Magnus Hagander
• pg_class char type should be "char"?
  • From: jian he
• Re: Postgres query doesn't accept double quote around schema name in query statement
  • From: Adrian Klaver
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: gzh
• Re: Postgres query doesn't accept double quote around schema name in query statement
  • From: Rob Sargent
• Re: Postgres query doesn't accept double quote around schema name in query statement
  • From: Adrian Klaver
• Re: Postgres query doesn't accept double quote around schema name in query statement
  • From: Christophe Pettus
• Re: Postgres query doesn't accept double quote around schema name in query statement
  • From: Tom Lane
• Postgres query doesn't accept double quote around schema name in query statement
  • From: Michael Xu
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Tom Lane
• Re: Re:Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Erik Wienhold
• Re: Differential Backups in Windows server
  • From: Erik Wienhold
• Re: Differential Backups in Windows server
  • From: Ravi Krishna
• Differential Backups in Windows server
  • From: Rajmohan Masa
• Re:Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: gzh
• Re: PostgreSQL in-transit compression for a client connection
  • From: Laurenz Albe
• Re: PostgreSQL in-transit compression for a client connection
  • From: Dominique Devienne
• Re: PostgreSQL in-transit compression for a client connection
  • From: Laurenz Albe
• Re: PostgreSQL in-transit compression for a client connection
  • From: Daniel Gustafsson
• PostgreSQL in-transit compression for a client connection
  • From: Tushar Takate
• Fwd: postgresql15-contrib installation on Amazon Linux 2 fails on Python shared lib dependency
  • From: Max Kremer
• Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'
  • From: Matthias Apitz
• Re: FW: Error!
  • From: postgresql439848
• Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'
  • From: Peter J. Holzer
• Re: VACUUM (INDEX_CLEANUP OFF) and GIN indexes
  • From: Christophe Pettus
• Re: VACUUM (INDEX_CLEANUP OFF) and GIN indexes
  • From: Peter Geoghegan
• VACUUM (INDEX_CLEANUP OFF) and GIN indexes
  • From: Christophe Pettus
• Re: murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Imre Samu
• Re: FW: Error!
  • From: Adrian Klaver
• Re: FW: Error!
  • From: postgresql439848
• Re: DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'
  • From: Ian Lawrence Barwick
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Erik Wienhold
• DBD::Pg (version 3.16.3) returns EMPTY char columns as 'undef'
  • From: Matthias Apitz
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: gzh
• Re: murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Erik Wienhold
• Re: murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Jagmohan Kaintura
• Re: murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Jeffrey Walton
• Re: wiki.postgres ​ Tighten trigger permission checks already resolved
  • From: Tom Lane
• Re: murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Erik Wienhold
• wiki.postgres ​ Tighten trigger permission checks already resolved
  • From: jian he
• Re: what happens if a failed transaction is not rolled back?
  • From: Merlin Moncure
• Re: what happens if a failed transaction is not rolled back?
  • From: Tom Lane
• murmur3 hash binary data migration from Oracle to PostgreSQL
  • From: Jagmohan Kaintura
• Re: what happens if a failed transaction is not rolled back?
  • From: Merlin Moncure
• Re: FW: Error!
  • From: Erik Wienhold
• Re: FW: Error!
  • From: Adrian Klaver
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: FW: Error!
  • From: Adrian Klaver
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: what happens if a failed transaction is not rolled back?
  • From: Tom Lane
• Re: what happens if a failed transaction is not rolled back?
  • From: David G. Johnston
• Re: what happens if a failed transaction is not rolled back?
  • From: David Wheeler
• Re: what happens if a failed transaction is not rolled back?
  • From: Luca Ferrari
• Re: [EXT] Re: SCROLLABLE/UPDATABLE cursor question
  • From: Garfield Lewis
• Re: [EXT] Re: SCROLLABLE/UPDATABLE cursor question
  • From: Garfield Lewis
• Re: what happens if a failed transaction is not rolled back?
  • From: David G. Johnston
• Re: what happens if a failed transaction is not rolled back?
  • From: Adrian Klaver
• Re: what happens if a failed transaction is not rolled back?
  • From: Adrian Klaver
• Re: [EXT] Re: SCROLLABLE/UPDATABLE cursor question
  • From: Tom Lane
• what happens if a failed transaction is not rolled back?
  • From: Siddharth Jain
• Re: [EXT] Re: SCROLLABLE/UPDATABLE cursor question
  • From: Adrian Klaver
• Re: [EXT] Re: SCROLLABLE/UPDATABLE cursor question
  • From: Garfield Lewis
• Re: alter table rename column can event trigger capture new column name
  • From: jian he
• alter table rename column can event trigger capture new column name
  • From: jian he
• Replicating / Updating Materialized views across databases
  • From: Alex Magnum
• Re: Why not use the calloc to replace malloc?
  • From: Tom Lane
• Re: Why not use the calloc to replace malloc?
  • From: Thorsten Glaser
• Re: Why not use the calloc to replace malloc?
  • From: Tom Lane
• Why not use the calloc to replace malloc?
  • From: Wen Yi
• Re: SCROLLABLE/UPDATABLE cursor question
  • From: Tom Lane
• SCROLLABLE/UPDATABLE cursor question
  • From: Garfield Lewis
• Re: How to verify postrgresql download on windows?
  • From: Matthias Apitz
• Re: How to verify postrgresql download on windows?
  • From: Ali M.
• Re: FW: Error!
  • From: Adrian Klaver
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: Why does the planner reduce the planned rows when filtering single values in an array
  • From: Isaiah Langford
• Re: Where to find the Makefile.global?
  • From: Tom Lane
• Where to find the Makefile.global?
  • From: Wen Yi
• Re: vacuum TOAST tables
  • From: senor
• Re: Why does the planner reduce the planned rows when filtering single values in an array
  • From: Tom Lane
• Re: HOT update: why must ALL indexes should be update?
  • From: Tom Lane
• HOT update: why must ALL indexes should be update?
  • From: Daniel Wu
• Why does the planner reduce the planned rows when filtering single values in an array
  • From: Isaiah Langford
• Re: missing something about json syntax
  • From: Marc Millas
• Unexpectedly huge memory usage (over 180x of work_mem) during hash join... confirmed by TopMemoryContext results (postgresql 13.10)
  • From: Maxim Boguk
• Re: vacuum TOAST tables
  • From: Laurenz Albe
• vacuum TOAST tables
  • From: senor
• Re: missing something about json syntax
  • From: Tom Lane
• Re: missing something about json syntax
  • From: Marc Millas
• Re: missing something about json syntax
  • From: Erik Wienhold
• missing something about json syntax
  • From: Marc Millas
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Bryn Llewellyn
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Laurenz Albe
• Re: Question about accessing partitions whose name includes the schema name and a period - is this correct?
  • From: Tom Lane
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: David G. Johnston
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Bryn Llewellyn
• How does pg index page optimize dead tuples?
  • From: jacktby@xxxxxxxxx
• Re: Question about accessing partitions whose name includes the schema name and a period - is this correct?
  • From: Erik Wienhold
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Adrian Klaver
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Bryn Llewellyn
• Re: Question about accessing partitions whose name includes the schema name and a period - is this correct?
  • From: Jay Stanley
• Re: Question about accessing partitions whose name includes the schema name and a period - is this correct?
  • From: Tom Lane
• Question about accessing partitions whose name includes the schema name and a period - is this correct?
  • From: Jay Stanley
• Re: What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Jeremy Smith
• What happened to the tip "It is good practice to create a role that has the CREATEDB and CREATEROLE privileges..."
  • From: Bryn Llewellyn
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Adrian Klaver
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Tom Lane
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: gzh
• Re: Joins of data-modifying CTE with the target table
  • From: Tom Lane
• Re: Joins of data-modifying CTE with the target table
  • From: Adrian Klaver
• Re: Joins of data-modifying CTE with the target table
  • From: Alex Bolenok
• Re: Joins of data-modifying CTE with the target table
  • From: Adrian Klaver
• Re: Joins of data-modifying CTE with the target table
  • From: Tom Lane
• Re: COPY RETURNING?
  • From: Adrian Klaver
• Joins of data-modifying CTE with the target table
  • From: Alex Bolenok
• Re: psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: Erik Wienhold
• psql:t_mstr.sql:994: ERROR: function to_char(numeric) does not exist
  • From: gzh
• COPY RETURNING?
  • From: Dominique Devienne
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Request for information about postgres version 15.2 stability
  • From: Stéphane Dunand
• ETCD for Patroni configuration error
  • From: Inzamam Shafiq
• Re: Request for information about postgres version 15.2 stability
  • From: Tom Lane
• Re: Logical Replication Sync Validation
  • From: Laurenz Albe
• Postgres as a LRU cache?
  • From: David Tinker
• Re: Request for information about postgres version 15.2 stability
  • From: Laurenz Albe
• Re: Question on SSI - Serializable Snapshot Isolation
  • From: Siddharth Jain
• Re: Request for information about postgres version 15.2 stability
  • From: Adrian Klaver
• Re: Logical Replication Sync Validation
  • From: Christophe Pettus
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: Logical Replication Sync Validation
  • From: Christophe Pettus
• Logical Replication Sync Validation
  • From: Robert Sjöblom
• Request for information about postgres version 15.2 stability
  • From: gayathri ramesh
• Fwd: Request for information about Postgres version 15.2 stability
  • From: gayathri ramesh
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Question on SSI - Serializable Snapshot Isolation
  • From: Tom Lane
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: Should I add a new schema for my application?
  • From: Laurenz Albe
• Question on SSI - Serializable Snapshot Isolation
  • From: Siddharth Jain
• Re: Suppress logging of "pg_hba.conf rejects connection for host"
  • From: Ron
• Re: cursor with hold must be save to disk?
  • From: 黄宁
• Re: PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements
  • From: Bryn Llewellyn
• Re: Call a Normal function inside a Trigger Function
  • From: FOUTE K. Jaurès
• Re: Call a Normal function inside a Trigger Function
  • From: Pavel Stehule
• Re: Call a Normal function inside a Trigger Function
  • From: Adrian Klaver
• Re: Call a Normal function inside a Trigger Function
  • From: FOUTE K. Jaurès
• Re: PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements
  • From: Adrian Klaver
• PL/pgSQL's "open cur for execute" provides workarouned... Re: cursors with prepared statements
  • From: Bryn Llewellyn
• RE: FW: Error!
  • From: Arquimedes Aguirre
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: Call a Normal function inside a Trigger Function
  • From: Pavel Stehule
• Re: Suppress logging of "pg_hba.conf rejects connection for host"
  • From: Erik Wienhold
• Re: Call a Normal function inside a Trigger Function
  • From: Erik Wienhold
• Suppress logging of "pg_hba.conf rejects connection for host"
  • From: ertan.kucukoglu
• Call a Normal function inside a Trigger Function
  • From: FOUTE K. Jaurès
• Re: FW: Error!
  • From: Adrian Klaver
• Re: FW: Error!
  • From: Adrian Klaver
• Re: cursors with prepared statements
  • From: Bryn Llewellyn
• Re: cursors with prepared statements
  • From: David G. Johnston
• Re: cursors with prepared statements
  • From: Bryn Llewellyn
• Logical replication failed with SSL SYSCALL error
  • From: shaurya jain
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: FW: Error!
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Peter J. Holzer
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Tom Lane
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Peter J. Holzer
• Should I add a new schema for my application?
  • From: Alexander Farber
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: David G. Johnston
• Re: Guidance on INSERT RETURNING order
  • From: Tom Lane
• Re: Guidance on INSERT RETURNING order
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Karsten Hilbert
• Re: Guidance on INSERT RETURNING order
  • From: David G. Johnston
• Re: Guidance on INSERT RETURNING order
  • From: David G. Johnston
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: David G. Johnston
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Peter J. Holzer
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Peter J. Holzer
• Re: SIze 0 in pg_stat_file, pg_stat_progress_copy
  • From: Marc Millas
• Re: [Extern] Re: Is a logical replication crash recovery safe?
  • From: GF
• Re: cursor with hold must be save to disk?
  • From: Laurenz Albe
• Re: cursor with hold must be save to disk?
  • From: Adrian Klaver
• SIze 0 in pg_stat_file, pg_stat_progress_copy
  • From: Marc Millas
• cursor with hold must be save to disk?
  • From: 黄宁
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Alban Hertroys
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Evgeny Morozov
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Thorsten Glaser
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Laurenz Albe
• Re: Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?
  • From: Bryn Llewellyn
• Re: Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?
  • From: Tom Lane
• Why does "fetch last from cur" always cause error 55000 for non-scrollable cursor?
  • From: Bryn Llewellyn
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Evgeny Morozov
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: Tom Lane
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: Adrian Klaver
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: Adrian Klaver
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: Ciprian Craciun
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Adrian Klaver
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Sebastien Flaesch
• Re: JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Ron
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Laurenz Albe
• JSON / ASP.NET AJAX Dates support in PostgreSQL
  • From: Sebastien Flaesch
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: Tom Lane
• Re: Unexpected behavior when combining `generated always` columns and update rules
  • From: David G. Johnston
• Unexpected behavior when combining `generated always` columns and update rules
  • From: Ciprian Craciun
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: [E] Re: parallel aggregation
  • From: Alexander Saydakov
• RE: FW: Error!
  • From: Arquimedes Aguirre
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Evgeny Morozov
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: pg_basebackup / recovery
  • From: Achilleas Mantzios
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: [E] Re: parallel aggregation
  • From: David Rowley
• Re: [E] Re: parallel aggregation
  • From: David Rowley
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: Guidance on INSERT RETURNING order
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: FW: Error!
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: FW: Error!
  • From: Greg Hennessy
• Re: pg_basebackup / recovery
  • From: Michael Paquier
• Re: Guidance on INSERT RETURNING order
  • From: Rob Sargent
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: Guidance on INSERT RETURNING order
  • From: Kirk Wolak
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Adrian Klaver
• Re: FW: Error!
  • From: Kirk Wolak
• Re: Guidance on INSERT RETURNING order
  • From: Kirk Wolak
• Re: TEXT column > 1Gb
  • From: Rob Sargent
• Re: TEXT column > 1Gb
  • From: Joe Carlson
• Re: TEXT column > 1Gb
  • From: Ron
• Re: TEXT column > 1Gb
  • From: Benedict Holland
• Re: TEXT column > 1Gb
  • From: Rob Sargent
• Re: TEXT column > 1Gb
  • From: Ron
• Re: TEXT column > 1Gb
  • From: Rob Sargent
• Re: TEXT column > 1Gb
  • From: Benedict Holland
• Re: TEXT column > 1Gb
  • From: Joe Carlson
• Re: TEXT column > 1Gb
  • From: Mark Dilger
• Re: TEXT column > 1Gb
  • From: Rob Sargent
• Re: FW: Error!
  • From: Adrian Klaver
• Re: TEXT column > 1Gb
  • From: Joe Carlson
• Re: Performance issue after migration from 9.4 to 15
  • From: Adrian Klaver
• Re: subscribe
  • From: Adrian Klaver
• Re: FW: Error!
  • From: Ron
• subscribe
  • From: Mike Bayer
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Tom Lane
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Daniel Gustafsson
• Re: Guidance on INSERT RETURNING order
  • From: John Howroyd
• Re: pg_basebackup / recovery
  • From: Achilleas Mantzios - cloud
• Re: parallel aggregation
  • From: David Rowley
• FW: Error!
  • From: Arquimedes Aguirre
• RE: Performance issue after migration from 9.4 to 15
  • From: Christian Schröder
• RE: Performance issue after migration from 9.4 to 15
  • From: Christian Schröder
• parallel aggregation
  • From: Alexander Saydakov
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• pg_basebackup / recovery
  • From: Fabrice Chapuis
• Re: Transaction Rollback errors
  • From: Tom Lane
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Michael Paquier
• Transaction Rollback errors
  • From: Siddharth Jain
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Rob Sargent
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Rob Sargent
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Mike Bayer
• Re: Guidance on INSERT RETURNING order
  • From: Thorsten Glaser
• Re: Guidance on INSERT RETURNING order
  • From: Federico
• Re: Guidance on INSERT RETURNING order
  • From: Tom Lane
• Re: Guidance on INSERT RETURNING order
  • From: Achilleas Mantzios
• Re: Guidance on INSERT RETURNING order
  • From: Adrian Klaver
• Re: Guidance on INSERT RETURNING order
  • From: Adrian Klaver
• Guidance on INSERT RETURNING order
  • From: Federico
• Re: TEXT column > 1Gb
  • From: Pavel Stehule
• Re: TEXT column > 1Gb
  • From: Rob Sargent
• TEXT column > 1Gb
  • From: Joe Carlson
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Evgeny Morozov
• Re: Performance issue after migration from 9.4 to 15
  • From: Tom Lane
• Re: Performance issue after migration from 9.4 to 15
  • From: David Rowley
• Performance issue after migration from 9.4 to 15
  • From: Christian Schröder
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Peter J. Holzer
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Karsten Hilbert
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Francisco Olarte
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Karsten Hilbert
• Re: Patroni vs pgpool II
  • From: Allan Nielsen
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Francisco Olarte
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Francisco Olarte
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Adrian Klaver
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Rob Sargent
• RE: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• RE: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• Re: Postgresql Upgrade from 10 to 14
  • From: Tom Lane
• Re: Postgresql Upgrade from 10 to 14
  • From: Adrian Klaver
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• Re: [EXTERNAL]: Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• Postgresql Upgrade from 10 to 14
  • From: thayanban thay
• Re: Replicate data from one standby server to another standby
  • From: Inzamam Shafiq
• Replicate data from one standby server to another standby
  • From: Atul Kumar
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Francisco Olarte
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Alban Hertroys
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Benedict Holland
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Adrian Klaver
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Israel Brewster
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Louis Tian
• Re: doc sql-grant.html Synopsis error?
  • From: Adrian Klaver
• Re: doc sql-grant.html Synopsis error?
  • From: Achilleas Mantzios
• doc sql-grant.html Synopsis error?
  • From: jian he
• Re: pg_ctlcluster is not stopping cluster
  • From: Jerry Sievers
• Re: pg_ctlcluster is not stopping cluster
  • From: Adrian Klaver
• RE: pg_ctlcluster is not stopping cluster
  • From: Telium Technical Support
• RE: pg_ctlcluster is not stopping cluster
  • From: Telium Technical Support
• RE: pg_ctlcluster is not stopping cluster
  • From: Thorsten Glaser
• Re: pg_ctlcluster is not stopping cluster
  • From: Thorsten Glaser
• RE: pg_ctlcluster is not stopping cluster
  • From: Telium Technical Support
• Re: pg_ctlcluster is not stopping cluster
  • From: Adrian Klaver
• Re: pg_ctlcluster is not stopping cluster
  • From: Boris Epstein
• pg_ctlcluster is not stopping cluster
  • From: Telium Technical Support
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Adrian Klaver
• Re: [EXTERNAL]: Re: UPSERT in Postgres
  • From: Adrian Klaver
• Re: Patroni vs pgpool II
  • From: Jehan-Guillaume de Rorthais
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Peter J. Holzer
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Michael Paquier
• Re: Patroni vs pgpool II
  • From: Ron
• Re: "PANIC: could not open critical system index 2662" - twice
  • From: Laurenz Albe
• Re: Patroni vs pgpool II
  • From: Jehan-Guillaume de Rorthais
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Jehan-Guillaume de Rorthais
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Nikolay Samokhvalov
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Nikolay Samokhvalov
• Re: Patroni vs pgpool II
  • From: Ron
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Backup schema without data
  • From: Brent Wood
• Re: Backup schema without data
  • From: Tom Lane
• Re: Backup schema without data
  • From: Michael Loftis
• Backup schema without data
  • From: Atul Kumar
• Re: PostgreSQL Mailing list public archives : search not working ...
  • From: Stephen Frost
• Re: UPSERT in Postgres
  • From: Benedict Holland
• Re: UPSERT in Postgres
  • From: Adrian Klaver
• Re: UPSERT in Postgres
  • From: Peter Geoghegan
• UPSERT in Postgres
  • From: Louis Tian
• PostgreSQL Mailing list public archives : search not working ...
  • From: Imre Samu
• "PANIC: could not open critical system index 2662" - twice
  • From: Evgeny Morozov
• Re: Patroni vs pgpool II
  • From: Jehan-Guillaume de Rorthais
• Re: R: Proposal: Shared Work Mem Area
  • From: Stephen Frost
• Re: Proposal: Shared Work Mem Area
  • From: Marco Fortina
• R: Proposal: Shared Work Mem Area
  • From: Marco Fortina
• Re: Proposal: Shared Work Mem Area
  • From: Stephen Frost
• Proposal: Shared Work Mem Area
  • From: Marco Fortina
• Re: Possible old and fixed bug in Postgres?
  • From: Tom Lane
• Re: Possible old and fixed bug in Postgres?
  • From: Ian Lawrence Barwick
• Re: Possible old and fixed bug in Postgres?
  • From: Steve Rogerson
• Re: PgOutput Replication Message Format - Differentiate between explicit NULL and Omitted Columns during Insert
  • From: Tom Lane
• Re: Possible old and fixed bug in Postgres?
  • From: Tom Lane
• Re: Possible old and fixed bug in Postgres?
  • From: Erik Wienhold
• Possible old and fixed bug in Postgres?
  • From: Steve Rogerson
• PgOutput Replication Message Format - Differentiate between explicit NULL and Omitted Columns during Insert
  • From: Pranav Hegde
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Inzamam Shafiq
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: Patroni vs pgpool II
  • From: Alexander Kukushkin
• Re: Patroni vs pgpool II
  • From: Tatsuo Ishii
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Adrian Klaver
• Re: Patroni vs pgpool II
  • From: cen
• Re: Patroni vs pgpool II
  • From: Jehan-Guillaume de Rorthais
• Re: DEFINER / INVOKER conundrum
  • From: Dominique Devienne
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Erik Wienhold
• Re: DEFINER / INVOKER conundrum
  • From: Erik Wienhold
• Re: DEFINER / INVOKER conundrum
  • From: walther
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: jian he
• Re: Oracle to PostgreSQL Migration
  • From: Jonny Saxon
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Adrian Klaver
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Erik Wienhold
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Adrian Klaver
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Erik Wienhold
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Adrian Klaver
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Tom Lane
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Erik Wienhold
• Re: DEFINER / INVOKER conundrum
  • From: Erik Wienhold
• Re: Patroni vs pgpool II
  • From: Ron
• Re: Very slow queries followed by checkpointer process killed with signal 9
  • From: Christoph Moench-Tegeder
• Re: DEFINER / INVOKER conundrum
  • From: Christoph Moench-Tegeder
• Re: Very slow queries followed by checkpointer process killed with signal 9
  • From: Joe Conway
• DEFINER / INVOKER conundrum
  • From: Dominique Devienne
• Re: Question on creating keys on partitioned tables
  • From: Laurenz Albe
• Re: PostgreSQL
  • From: Laurenz Albe
• RE: Cannot terminate backend
  • From: Arnaud Lesauvage
• Patroni vs pgpool II
  • From: Inzamam Shafiq
• Re: Very slow queries followed by checkpointer process killed with signal 9
  • From: Tom Lane
• Re: Very slow queries followed by checkpointer process killed with signal 9
  • From: Jason McLaurin
• Re: What permissions are needed to drop a column from a table in postgres?
  • From: David G. Johnston
• What permissions are needed to drop a column from a table in postgres?
  • From: Siddharth Jain
• Re: Very slow queries followed by checkpointer process killed with signal 9
  • From: Tom Lane
• Very slow queries followed by checkpointer process killed with signal 9
  • From: Jason McLaurin
• Re: PostgreSQL
  • From: Joseph Kennedy
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Adrian Klaver
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Tom Lane
• Re: ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: Erik Wienhold
• Support logical replication of DDLs
  • From: Phil Florent
• ​jsonb @@ jsonpath operator doc: ​Only the first item of the result is taken into account
  • From: jian he
• Re: My tests show that a WITH HOLD cursor has subtly different semantics from a WITHOUT HOLD cursor
  • From: Bryn Llewellyn
• Re: My tests show that a WITH HOLD cursor has subtly different semantics from a WITHOUT HOLD cursor
  • From: David G. Johnston
• My tests show that a WITH HOLD cursor has subtly different semantics from a WITHOUT HOLD cursor
  • From: Bryn Llewellyn
• Re: Question on creating keys on partitioned tables
  • From: Siddharth Jain
• Re: Question on creating keys on partitioned tables
  • From: Tom Lane
• Re: Cannot terminate backend
  • From: Paul Ramsey
• Re: Question on creating keys on partitioned tables
  • From: Siddharth Jain
• RE: Cannot terminate backend
  • From: Arnaud Lesauvage
• Re: Cannot terminate backend
  • From: Laurenz Albe
• Re: Question on creating keys on partitioned tables
  • From: Laurenz Albe
• Cannot terminate backend
  • From: Arnaud Lesauvage
• Re: libpq: COPY FROM STDIN BINARY of arrays
  • From: Dominique Devienne
• Question on creating keys on partitioned tables
  • From: Siddharth Jain
• Re: recovery long after startup
  • From: Tom Lane
• recovery long after startup
  • From: Rébeli-Szabó Tamás
• Re: Do BRIN indexes support MIN/MAX?
  • From: Andrey Klochkov
• Re: Multilang text search. Is this correct?
  • From: Tom Lane
• Re: Using CTID system column as a "temporary" primary key
  • From: Peter J. Holzer
• Re: libpq: COPY FROM STDIN BINARY of arrays
  • From: Tom Lane
• libpq: COPY FROM STDIN BINARY of arrays
  • From: Dominique Devienne
• Re: Using CTID system column as a "temporary" primary key
  • From: Laurenz Albe
• Re: Using CTID system column as a "temporary" primary key
  • From: Dominique Devienne
• Re: Get dead tuples data
  • From: David Rowley
• Re: Using CTID system column as a "temporary" primary key
  • From: Francisco Olarte
• Get dead tuples data
  • From: 任重
• Multilang text search. Is this correct?
  • From: Florents Tselai
• Re: Using CTID system column as a "temporary" primary key
  • From: Dominique Devienne
• Re: Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• Re: Do BRIN indexes support MIN/MAX?
  • From: Vladimir Sitnikov
• Re: Do BRIN indexes support MIN/MAX?
  • From: David Rowley
• Re: Do BRIN indexes support MIN/MAX?
  • From: Vladimir Sitnikov
• Re: Do BRIN indexes support MIN/MAX?
  • From: Tom Lane
• Re: Do BRIN indexes support MIN/MAX?
  • From: Julien Rouhaud
• Re: Do BRIN indexes support MIN/MAX?
  • From: Vladimir Sitnikov
• Re: COPY and custom datestyles. Or some other technique?
  • From: David G. Johnston
• Re: COPY and custom datestyles. Or some other technique?
  • From: Ron
• Re: COPY and custom datestyles. Or some other technique?
  • From: David G. Johnston
• Re: COPY and custom datestyles. Or some other technique?
  • From: Ron
• Re: COPY and custom datestyles. Or some other technique?
  • From: Ron
• Re: COPY and custom datestyles. Or some other technique?
  • From: Thorsten Glaser
• Re: COPY and custom datestyles. Or some other technique?
  • From: Adrian Klaver
• Re: COPY and custom datestyles. Or some other technique?
  • From: Adrian Klaver
• COPY and custom datestyles. Or some other technique?
  • From: Ron
• Re: Do BRIN indexes support MIN/MAX?
  • From: Andrey Klochkov
• Re: Do BRIN indexes support MIN/MAX?
  • From: Francisco Olarte
• Re: Using CTID system column as a "temporary" primary key
  • From: Francisco Olarte
• Re: Using CTID system column as a "temporary" primary key
  • From: Alban Hertroys
• Re: Do BRIN indexes support MIN/MAX?
  • From: Vladimir Sitnikov
• Re: Using CTID system column as a "temporary" primary key
  • From: Adrian Klaver
• Re: Using CTID system column as a "temporary" primary key
  • From: Christophe Pettus
• Re: Using CTID system column as a "temporary" primary key
  • From: Adrian Klaver
• 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
• Do BRIN indexes support MIN/MAX?
  • From: Andrey Klochkov
• Re: Using CTID system column as a "temporary" primary key
  • From: Peter J. Holzer
• Re: Using CTID system column as a "temporary" primary key
  • From: Laurenz Albe
• Re: Using CTID system column as a "temporary" primary key
  • From: Adrian Klaver
• 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: libpq: empty arrays have rank 0 in binary results? whatever the type's rank?
  • From: Dominique Devienne
• Re: libpq: empty arrays have rank 0 in binary results? whatever the type's rank?
  • From: Tom Lane
• libpq: empty arrays have rank 0 in binary results? whatever the type's rank?
  • From: Dominique Devienne
• Re: Move from MySQL to PostgreSQL
  • From: Thomas Kellerer
• Move from MySQL to PostgreSQL
  • From: basti
• Re: Using CTID system column as a "temporary" primary key
  • From: Laurenz Albe
• Re: How are the SELECT queries reconstructed in pg_views
  • From: Adrian Klaver
• Re: How are the SELECT queries reconstructed in pg_views
  • From: Adrian Klaver
• How are the SELECT queries reconstructed in pg_views
  • From: Julius de Bruijn
• Re: Using CTID system column as a "temporary" primary key
  • From: Kirk Wolak
• Re: Cluster table based on grand parent?
  • From: Ron
• Re: Cluster table based on grand parent?
  • From: Rob Sargent
• Re: Using CTID system column as a "temporary" primary key
  • From: Maciek Sakrejda
• Re: Cluster table based on grand parent?
  • From: Dominique Devienne
• Re: Cluster table based on grand parent?
  • From: Ron
• Re: Patroni, slots, and expiring WALs
  • From: Peter J. Holzer
• Re: Patroni, slots, and expiring WALs
  • From: Peter J. Holzer
• Re: Cluster table based on grand parent?
  • From: Dominique Devienne
• Re: Patroni, slots, and expiring WALs
  • From: Peter J. Holzer
• Re: Patroni, slots, and expiring WALs
  • From: Alexander Kukushkin
• Re: Cluster table based on grand parent?
  • From: Peter J. Holzer
• Re: Patroni, slots, and expiring WALs
  • From: Jeremy Smith
• Patroni, slots, and expiring WALs
  • From: Peter J. Holzer
• Re: Cluster table based on grand parent?
  • From: Adrian Klaver
• Re: Using CTID system column as a "temporary" primary key
  • From: Sebastien Flaesch
• Re: Plans for ON DELETE CASCADE? Which index is used, if at all?
  • From: Adrian Klaver
• Re: Plans for ON DELETE CASCADE? Which index is used, if at all?
  • From: Dominique Devienne
• Re: Plans for ON DELETE CASCADE? Which index is used, if at all?
  • From: Tom Lane
• Cluster table based on grand parent?
  • From: Dominique Devienne
• 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