Postgresql General Discussion

• Thread Index

• Re: pg_restore scan
  • From: R Wahyudi
• Re: encoding problem while inictial copy in logical replication
  • From: Adrian Klaver
• Re: pg_restore scan
  • From: Adrian Klaver
• Re: EDB Windows Installer on Windows Server 2025
  • From: Adrian Klaver
• Re: Index (primary key) corrupt?
  • From: Adrian Klaver
• Re: How do I specify the NetworkService user to the postgres installer.
  • From: Adrian Klaver
• Re: Index (primary key) corrupt?
  • From: Ron Johnson
• Re: pg_restore scan
  • From: Ron Johnson
• Re: pg_restore scan
  • From: Adrian Klaver
• Re: Silent data corruption in PostgreSQL 17 - how to detect it proactively?
  • From: Vladlen Popolitov
• Offline PostgreSQL installation: what are the rpm packages to install ?
  • From: COURTAULT Francois
• Re: Offline PostgreSQL installation: what are the rpm packages to install ?
  • From: Ron Johnson
• RE: Offline PostgreSQL installation: what are the rpm packages to install ?
  • From: COURTAULT Francois
• Re: Offline PostgreSQL installation: what are the rpm packages to install ?
  • From: Tom Lane
• RE: Offline PostgreSQL installation: what are the rpm packages to install ?
  • From: COURTAULT Francois
• Why analyze reports 30000 pages and rows scanned. Why not just rows?
  • From: David Mullineux
• Re: Why analyze reports 30000 pages and rows scanned. Why not just rows?
  • From: Tom Lane
• Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• vacuum analyze query performance - help me understand
  • From: Scot Kreienkamp
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: vacuum analyze query performance - help me understand
  • From: Tom Lane
• RE: vacuum analyze query performance - help me understand
  • From: Scot Kreienkamp
• Re: vacuum analyze query performance - help me understand
  • From: David G. Johnston
• RE: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Scot Kreienkamp
• Domains vs data types
  • From: Ertan Küçükoglu
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Alban Hertroys
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Ron Johnson
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Pawel Veselov
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  • From: Achilleas Mantzios
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Tom Lane
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Re: Domains vs data types
  • From: Adrian Klaver
• Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  • From: Adrian Klaver
• Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  • From: Paul A Jungwirth
• Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  • From: Tom Lane
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: vacuum analyze query performance - help me understand
  • From: Greg Sabino Mullane
• Re: Domains vs data types
  • From: Greg Sabino Mullane
• Re: Domains vs data types
  • From: Ron Johnson
• Re: pg_upgrade from 18beta1 -> 18beta3 - problem with btree_gist contrib module / extension
  • From: Tom Lane
• Re: Domains vs data types
  • From: Ron Clarke
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Domains vs data types
  • From: David G. Johnston
• MS SQL to Postgres
  • From: KK CHN
• Re: Domains vs data types
  • From: Florents Tselai
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Rob Sargent
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Thom Brown
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: MS SQL to Postgres
  • From: Adrian Klaver
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Alban Hertroys
• Re: MS SQL to Postgres
  • From: Alban Hertroys
• Re: MS SQL to Postgres
  • From: Justin
• Re: MS SQL to Postgres
  • From: Avinash Vallarapu
• Re: MS SQL to Postgres
  • From: Adrian Klaver
• Re: Domains vs data types
  • From: Dominique Devienne
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Thom Brown
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Q: GRANT ... WITH ADMIN on PG 17
  • From: Karsten Hilbert
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Karsten Hilbert
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Adrian Klaver
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Karsten Hilbert
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Karsten Hilbert
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Adrian Klaver
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: David G. Johnston
• Re: Domains vs data types
  • From: Merlin Moncure
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Dominique Devienne
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Dominique Devienne
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Chris Wilson
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Laurenz Albe
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Pavel Stehule
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Adrian Klaver
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Tom Lane
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: Tom Lane
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Pavel Luzanov
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: Dominique Devienne
• Re: Streaming replica hangs periodically for ~ 1 second - how to diagnose/debug
  • From: hubert depesz lubaczewski
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Re: Strange deadlock with object/target of lock : transaction
  • From: Adrian Klaver
• Re: DISABLE TRIGGER doc wrong?
  • From: Adrian Klaver
• Re: DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• Re: DISABLE TRIGGER doc wrong?
  • From: Adrian Klaver
• Re: DISABLE TRIGGER doc wrong?
  • From: Pavel Luzanov
• Re: DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• Re: DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• Re: Q: GRANT ... WITH ADMIN on PG 17
  • From: DINESH NAIR
• Re: Strange deadlock with object/target of lock : transaction
  • From: Laurenz Albe
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Feature request: A method to configure client-side TLS ciphers for streaming replication
  • From: xx Z
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Re: DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: xx Z
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: Laurenz Albe
• How to configure client-side TLS ciphers for streaming replication?
  • From: xx Z
• Re: Feature request: A method to configure client-side TLS ciphers for streaming replication
  • From: xx Z
• Re: DISABLE TRIGGER doc wrong?
  • From: Ron Johnson
• Re: DISABLE TRIGGER doc wrong?
  • From: Ron Johnson
• Re: Feature request: A method to configure client-side TLS ciphers for streaming replication
  • From: Ron Johnson
• Re: DISABLE TRIGGER doc wrong?
  • From: Dominique Devienne
• DMS error where postgres is the destination
  • From: Siraj G
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: Rob Sargent
• Re: DISABLE TRIGGER doc wrong?
  • From: Tom Lane
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: DINESH NAIR
• Re: Feature request: A method to configure client-side TLS ciphers for streaming replication
  • From: Ron Johnson
• In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: David G. Johnston
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: Laurenz Albe
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Ron Johnson
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Ron Johnson
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Ron Johnson
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Greg Sabino Mullane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Ron Johnson
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Ron Johnson
• psql --html and to_char()
  • From: Ron Johnson
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: How to configure client-side TLS ciphers for streaming replication?
  • From: Daniel Gustafsson
• Re: psql --html and to_char()
  • From: Greg Sabino Mullane
• Re: psql --html and to_char()
  • From: Ron Johnson
• Saw some strange behavior when using `INSERT ON CONFLICT` inside a transaction.
  • From: Sagar Tiwari
• Re: Saw some strange behavior when using `INSERT ON CONFLICT` inside a transaction.
  • From: Achilleas Mantzios
• Re: Saw some strange behavior when using `INSERT ON CONFLICT` inside a transaction.
  • From: Nico Williams
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Q: limit the length of log file entries?
  • From: Albrecht Dreß
• Re: Q: limit the length of log file entries?
  • From: Adrian Klaver
• Re: Q: limit the length of log file entries?
  • From: Tom Lane
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Álvaro Herrera
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Adrian Klaver
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Adrian Klaver
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Dimitrios Apostolou
• Re: Q: limit the length of log file entries?
  • From: Albrecht Dreß
• Re: Q: limit the length of log file entries?
  • From: Albrecht Dreß
• Re: Q: limit the length of log file entries?
  • From: Adrian Klaver
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: In-order pg_dump (or in-order COPY TO)
  • From: Achilleas Mantzios
• Debugging query performance in postgres
  • From: veem v
• Re: Q: limit the length of log file entries?
  • From: Adrian Klaver
• Re: Debugging query performance in postgres
  • From: Adrian Klaver
• Re: Q: limit the length of log file entries?
  • From: Adrian Klaver
• Re: Q: limit the length of log file entries?
  • From: Albrecht Dreß
• Re: Debugging query performance in postgres
  • From: veem v
• Re: Debugging query performance in postgres
  • From: Adrian Klaver
• Re: Debugging query performance in postgres
  • From: Ron Johnson
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: PALAYRET Jacques
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: David G. Johnston
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: Tom Lane
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: Ron Johnson
• LWLock SerializableFinishedList
  • From: Alec Cozens
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: Merlin Moncure
• Re: LWLock SerializableFinishedList
  • From: Justin
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: PALAYRET Jacques
• RE: LWLock SerializableFinishedList
  • From: Alec Cozens
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: Greg Sabino Mullane
• Fast switchover
  • From: legrand legrand
• RE: LWLock SerializableFinishedList
  • From: Alec Cozens
• RE: Fast switchover
  • From: Klaus Darilion
• Re: Fast switchover
  • From: Ron Johnson
• Re: PostgreSQL include directive in plpgsql language PL/pgSQL
  • From: Merlin Moncure
• Re: Fast switchover
  • From: Ron Johnson
• Re: Fast switchover
  • From: Laurenz Albe
• RE: Fast switchover
  • From: Klaus Darilion
• Re: Re : Fast switchover
  • From: Laurenz Albe
• Re : Fast switchover
  • From: legrand legrand
• Re: MVCC and all that...
  • From: Justin
• Re: MVCC and all that...
  • From: Adrian Klaver
• Re: MVCC and all that...
  • From: Ron Johnson
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• Re: MVCC and all that...
  • From: Ron Johnson
• Re: MVCC and all that...
  • From: Álvaro Herrera
• Re: MVCC and all that...
  • From: Merlin Moncure
• Re: MVCC and all that...
  • From: Nico Williams
• Re: MVCC and all that...
  • From: Nico Williams
• Re: MVCC and all that...
  • From: Ron Johnson
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• Re: How to use \restrict or \unrestirct in python
  • From: Adrian Klaver
• Re: pg_restore scan
  • From: R Wahyudi
• EDB Windows Installer on Windows Server 2025
  • From: Daniel Westermann (DWE)
• Re: pg_restore scan
  • From: Adrian Klaver
• Re: MVCC and all that...
  • From: Rob Sargent
• Re: MVCC and all that...
  • From: Merlin Moncure
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• MVCC and all that...
  • From: Ellen Allhatatlan
• Re: LWLock SerializableFinishedList
  • From: Justin
• Re: LWLock SerializableFinishedList
  • From: Justin
• Re: MVCC and all that...
  • From: Merlin Moncure
• Re: MVCC and all that...
  • From: Justin
• Re: MVCC and all that...
  • From: Ron Johnson
• Re: MVCC and all that...
  • From: Justin
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• Re: MVCC and all that...
  • From: Adrian Klaver
• Re: [Announcement] ​A Bitemporal Solution for PostgreSQL (Beta)
  • From: Lorusso Domenico
• [Announcement] ​A Bitemporal Solution for PostgreSQL (Beta)
  • From: Lorusso Domenico
• Re: MVCC and all that...
  • From: Merlin Moncure
• Re: MVCC and all that...
  • From: Pavel Stehule
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: jian he
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Dominique Devienne
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Tom Lane
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Álvaro Herrera
• Re: MVCC and all that...
  • From: Ellen Allhatatlan
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: MVCC and all that...
  • From: Justin
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Tom Lane
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Tom Lane
• Re: Latest patches break one of our unit-test, related to RLS
  • From: Laurenz Albe
• Silent data corruption in PostgreSQL 17 - how to detect it proactively?
  • From: Pawel Kudzia
• Re: Silent data corruption in PostgreSQL 17 - how to detect it proactively?
  • From: Laurenz Albe
• Re: Silent data corruption in PostgreSQL 17 - how to detect it proactively?
  • From: Pawel Kudzia
• Re: Silent data corruption in PostgreSQL 17 - how to detect it proactively?
  • From: Laurenz Albe
• Re: Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Re: Strange deadlock with object/target of lock : transaction
  • From: Adrian Klaver
• Re: help with upgrade from v15 to v16 rhel z/linux needed
  • From: Adrian Klaver
• help with upgrade from v15 to v16 rhel z/linux needed
  • From: Evelina Angelova
• Strange deadlock with object/target of lock : transaction
  • From: Achilleas Mantzios
• Re: Questions about the continuity of WAL archiving
  • From: Adrian Klaver
• Re: Questions about the continuity of WAL archiving
  • From: Justin
• Re: Bitnami deprecation
  • From: Rachel Roch
• Re: pgbackrest check info fails without success
  • From: KK CHN
• Re: pgbackrest check info fails without success
  • From: Ruben Morais
• Re: pgbackrest check info fails without success
  • From: KK CHN
• Re: pgbackrest check info fails without success
  • From: Ruben Morais
• pgbackrest check info fails without success
  • From: KK CHN
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Laurenz Albe
• Re: Questions about the continuity of WAL archiving
  • From: Justin
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Questions about the continuity of WAL archiving
  • From: Ron Johnson
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Questions about the continuity of WAL archiving
  • From: Adrian Klaver
• Re: Backups with filesystem snapshots
  • From: Bruce Momjian
• Re: Questions about the continuity of WAL archiving
  • From: Ron Johnson
• Re: Questions about the continuity of WAL archiving
  • From: Bob Jolliffe
• Re: Questions about the continuity of WAL archiving
  • From: Adrian Klaver
• Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export
  • From: Adrian Klaver
• Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export
  • From: Ron Johnson
• Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export
  • From: Ian Huang
• Re: Bitnami deprecation
  • From: Daniel Gustafsson
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export
  • From: Greg Sabino Mullane
• Re: Backups with filesystem snapshots
  • From: Greg Sabino Mullane
• Re: Bitnami deprecation
  • From: Adrian Klaver
• Re: Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row
  • From: Greg Sabino Mullane
• Bitnami deprecation
  • From: Smith
• Re: Backups with filesystem snapshots
  • From: Ron Johnson
• Backups with filesystem snapshots
  • From: Nick Cleaton
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Charles Qi
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Laurenz Albe
• Re: Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row
  • From: Akashkiran Shivakumar
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Adrian Klaver
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Charles Qi
• Re: Questions about the continuity of WAL archiving
  • From: Ron Johnson
• Re: Questions about the continuity of WAL archiving
  • From: Greg Sabino Mullane
• Re: Questions about the continuity of WAL archiving
  • From: Adrian Klaver
• Re: Libpq.dll
  • From: suporte02@xxxxxxxxxxxxxxxxxxx
• Re: CALL and named parameters
  • From: Dominique Devienne
• Re: Questions about the continuity of WAL archiving
  • From: px shi
• Re: Questions about the continuity of WAL archiving
  • From: Adrian Klaver
• Questions about the continuity of WAL archiving
  • From: px shi
• Re: CALL and named parameters
  • From: Tom Lane
• Re: CALL and named parameters
  • From: Christoph Moench-Tegeder
• Re: Libpq.dll
  • From: Adrian Klaver
• Re: CALL and named parameters
  • From: Tom Lane
• Re: CALL and named parameters
  • From: Dominique Devienne
• Re: CALL and named parameters
  • From: Tom Lane
• Re: CALL and named parameters
  • From: Dominique Devienne
• Re: CALL and named parameters
  • From: Tom Lane
• Re: CALL and named parameters
  • From: Dominique Devienne
• Re: CALL and named parameters
  • From: Pavel Stehule
• Re: CALL and named parameters
  • From: David G. Johnston
• Re: CALL and named parameters
  • From: Dominique Devienne
• Re: Libpq.dll
  • From: suporte02@xxxxxxxxxxxxxxxxxxx
• Re: Libpq.dll
  • From: suporte02@xxxxxxxxxxxxxxxxxxx
• Re: Approach for DB migration
  • From: Ron Johnson
• Re: Approach for DB migration
  • From: Siraj G
• Re: Approach for DB migration
  • From: Ron Johnson
• Approach for DB migration
  • From: Siraj G
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Adrian Klaver
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: David G. Johnston
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: David G. Johnston
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: David G. Johnston
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Adrian Klaver
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Ron Johnson
• Re: Libpq.dll
  • From: Adrian Klaver
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: CALL and named parameters
  • From: Christoph Moench-Tegeder
• Re: Libpq.dll
  • From: Merlin Moncure
• Re: When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Adrian Klaver
• Re: CALL and named parameters
  • From: Adrian Klaver
• Re: CALL and named parameters
  • From: Pavel Stehule
• CALL and named parameters
  • From: Dominique Devienne
• Re: Libpq.dll
  • From: Adrian Klaver
• Libpq.dll
  • From: suporte02@xxxxxxxxxxxxxxxxxxx
• When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID
  • From: Charles Qi
• Re: Stored procedures or raw queries
  • From: Marco Torres
• Re: Stored procedures or raw queries
  • From: Dominique Devienne
• Re: Stored procedures or raw queries
  • From: Simon Connah
• Re: Stored procedures or raw queries
  • From: Philip Semanchuk
• Re: Stored procedures or raw queries
  • From: Justin Swanhart
• Re: Stored procedures or raw queries
  • From: Pavel Stehule
• Stored procedures or raw queries
  • From: Simon Connah
• Re: PGDG16 repository error - repomd.xml.asc is empty
  • From: Aleš Zelený
• Re: PGDG16 repository error - repomd.xml.asc is empty
  • From: Adrian Klaver
• Re: Notices not printed by PQtrace
  • From: Dominique Devienne
• Re: Notices not printed by PQtrace
  • From: Álvaro Herrera
• Notices not printed by PQtrace
  • From: Dominique Devienne
• Re: PGDG16 repository error - repomd.xml.asc is empty
  • From: Aleš Zelený
• Re: PGDG16 repository error - repomd.xml.asc is empty
  • From: Aleš Zelený
• PGDG16 repository error - repomd.xml.asc is empty
  • From: Aleš Zelený
• Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export
  • From: Ian Huang
• Re: What is the specific release date of PG18?
  • From: David G. Johnston
• Re: What is the specific release date of PG18?
  • From: David G. Johnston
• Re: What is the specific release date of PG18?
  • From: David Rowley
• What is the specific release date of PG18?
  • From: 矫顺田
• Re: Get info about the index
  • From: Adrian Klaver
• Re: Get info about the index
  • From: Igor Korot
• Re: Get info about the index
  • From: Jon Zeppieri
• Re: Get info about the index
  • From: Adrian Klaver
• Re: Get info about the index
  • From: Igor Korot
• Re: Failing to allocate memory when I think it shouldn't
  • From: Christoph Moench-Tegeder
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Álvaro Herrera
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Adrian Klaver
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: David G. Johnston
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Adrian Klaver
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Tom Lane
• Re: Yet more ROLE changes in v18 beta1???
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Guillaume Lelarge
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Adrian Klaver
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Adrian Klaver
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Adrian Klaver
• Re: Failing to allocate memory when I think it shouldn't
  • From: Siraj G
• SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function
  • From: Dominique Devienne
• Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row
  • From: Akashkiran Shivakumar
• Re: Regarding logical replication issues with PostgreSQL versions 16and above
  • From: Laurenz Albe
• Re: Regarding logical replication issues with PostgreSQL versions 16and above
  • From: yexiu-glory
• Re: Get info about the index
  • From: Igor Korot
• Re: Get info about the index
  • From: Laurenz Albe
• Re: Get info about the index
  • From: Igor Korot
• Re: Get info about the index
  • From: Laurenz Albe
• Re: Get info about the index
  • From: Igor Korot
• Re: Get info about the index
  • From: Laurenz Albe
• Re: Get info about the index
  • From: David Barbour
• Re: Regarding logical replication issues with PostgreSQL versions 16 and above
  • From: DINESH NAIR
• Re: Get info about the index
  • From: Jon Zeppieri
• Re: Get info about the index
  • From: Laurenz Albe
• Re: Get info about the index
  • From: Igor Korot
• Re: Get info about the index
  • From: Christophe Pettus
• Re: Get info about the index
  • From: Igor Korot
• Re: Possible causes of high_replay lag, given replication settings?
  • From: Jon Zeppieri
• Re: Get info about the index
  • From: Tom Lane
• Re: Get info about the index
  • From: Adrian Klaver
• Re: Get info about the index
  • From: David G. Johnston
• Re: Get info about the index
  • From: Robert Sjöblom
• Re: Get info about the index
  • From: Adrian Klaver
• Get info about the index
  • From: Igor Korot
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Vladimir Churyukin
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Vladimir Churyukin
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: Possible causes of high_replay lag, given replication settings?
  • From: Greg Sabino Mullane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Laurenz Albe
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Adrian Klaver
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Tom Lane
• Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Adrian Klaver
• PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array
  • From: Rumpi Gravenstein
• Re: Upper / lower case keys in JSON objects
  • From: Adrian Klaver
• Re: Sorting by respecting diacritics/accents
  • From: Laurenz Albe
• Re: Possible causes of high_replay lag, given replication settings?
  • From: Jon Zeppieri
• Re: Upper / lower case keys in JSON objects
  • From: Mark
• Upper / lower case keys in JSON objects
  • From: Mark
• Sorting by respecting diacritics/accents
  • From: JānisE
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: Is there any limit on the number of rows to import using copy command
  • From: Adrian Klaver
• Re: Is there any limit on the number of rows to import using copy command
  • From: Ron Johnson
• Re: Is there any limit on the number of rows to import using copy command
  • From: sivapostgres@xxxxxxxxx
• Re: Is there any limit on the number of rows to import using copy command
  • From: sivapostgres@xxxxxxxxx
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Marco Torres
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Jeff Ross
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Nico Williams
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Nico Williams
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: Is there any limit on the number of rows to import using copy command
  • From: David Barbour
• Re: Is there any limit on the number of rows to import using copy command
  • From: Adrian Klaver
• Re: Is there any limit on the number of rows to import using copy command
  • From: sivapostgres@xxxxxxxxx
• Re: Possible causes of high_replay lag, given replication settings?
  • From: Nick Cleaton
• Re: Is there any limit on the number of rows to import using copy command
  • From: Merlin Moncure
• Re: Is there any limit on the number of rows to import using copy command
  • From: Adrian Klaver
• Re: Is there any limit on the number of rows to import using copy command
  • From: Laurenz Albe
• Re: Is there any limit on the number of rows to import using copy command
  • From: sivapostgres@xxxxxxxxx
• Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture
  • From: Jehan-Guillaume de Rorthais
• Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture
  • From: Achilleas Mantzios
• Re: Is there any limit on the number of rows to import using copy command
  • From: Laurenz Albe
• Re: Is there any limit on the number of rows to import using copy command
  • From: sivapostgres@xxxxxxxxx
• Re: Wrapping a select in another select makes it slower
  • From: Peter J. Holzer
• Re: PgBouncer Prepared Statement ERROR
  • From: Achilleas Mantzios
• Re: Wrapping a select in another select makes it slower
  • From: David Rowley
• Wrapping a select in another select makes it slower
  • From: Peter J. Holzer
• Re: Request for Feedback on PostgreSQL HA + Load Balancing Architecture
  • From: Greg Sabino Mullane
• Re: Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU
  • From: Laurenz Albe
• Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU
  • From: Klaus Darilion
• Re: Performance of JSON type in postgres
  • From: Adrian Klaver
• Re: Performance of JSON type in postgres
  • From: Ron Johnson
• Re: Performance of JSON type in postgres
  • From: veem v
• Re: Performance of JSON type in postgres
  • From: Adrian Klaver
• Re: Performance of JSON type in postgres
  • From: veem v
• Possible causes of high_replay lag, given replication settings?
  • From: Jon Zeppieri
• Re: Regarding logical replication issues with PostgreSQL versions 16 and above
  • From: Laurenz Albe
• Re: PgBouncer Prepared Statement ERROR
  • From: Laurenz Albe
• Re: PgBouncer Prepared Statement ERROR
  • From: Greg Sabino Mullane
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Seref Arikan
• PgBouncer Prepared Statement ERROR
  • From: KK CHN
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Regarding logical replication issues with PostgreSQL versions 16 and above
  • From: yexiu-glory
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Seref Arikan
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Laurenz Albe
• Re: Should we document the cost of pg_database_size()? Alternatives?
  • From: Ron Johnson
• Re: Should we document the cost of pg_database_size()? Alternatives?
  • From: Craig Ringer
• Should we document the cost of pg_database_size()? Alternatives?
  • From: Craig Ringer
• PostgreSQL on S3-backed Block Storage with Near-Local Performance
  • From: Pierre Barre
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Ron Johnson
• Re: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication
  • From: Kiran K V
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Tom Lane
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Greg Sabino Mullane
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Laurenz Albe
• Re: PgBouncer-Postgres : un supported startup parameter statement_timeout
  • From: Adrian Klaver
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Ron Johnson
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re:Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
  • From: gzh
• Re: PgBouncer-Postgres : un supported startup parameter statement_timeout
  • From: Achilleas Mantzios
• Re: PgBouncer-Postgres : un supported startup parameter statement_timeout
  • From: Robert Sjöblom
• Re: PgBouncer-Postgres : un supported startup parameter statement_timeout
  • From: Achilleas Mantzios
• PgBouncer-Postgres : un supported startup parameter statement_timeout
  • From: KK CHN
• Re: Removing terminal period from varchar string in table column
  • From: Rich Shepard
• Re: Removing terminal period from varchar string in table column
  • From: Rich Shepard
• Re: Removing terminal period from varchar string in table column
  • From: Thom Brown
• Re: Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication
  • From: DINESH NAIR
• Re: Removing terminal period from varchar string in table column
  • From: Rich Shepard
• Re: Removing terminal period from varchar string in table column
  • From: Thom Brown
• Re: Removing terminal period from varchar string in table column
  • From: Jeff Ross
• Re: Performance of JSON type in postgres
  • From: Merlin Moncure
• Removing terminal period from varchar string in table column
  • From: Rich Shepard
• Re: optimizing number of workers
  • From: Greg Hennessy
• Re: Regarding query optimisation (select for update)
  • From: Greg Sabino Mullane
• Re: Regarding query optimisation (select for update)
  • From: Tom Lane
• Re: Regarding query optimisation (select for update)
  • From: Laurenz Albe
• Re: Regarding query optimisation (select for update)
  • From: Andy Huang
• Re: Regarding query optimisation (select for update)
  • From: Durgamahesh Manne
• Re: Regarding query optimisation (select for update)
  • From: Laurenz Albe
• Re: Syntax error needs explanation [RESOLVED]
  • From: Rich Shepard
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Regarding query optimisation (select for update)
  • From: Durgamahesh Manne
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Laurenz Albe
• Re: Syntax error needs explanation [RESOLVED]
  • From: David G. Johnston
• Re: Syntax error needs explanation [RESOLVED]
  • From: Laurenz Albe
• RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: Hayato Kuroda (Fujitsu)
• Re: Syntax error needs explanation [RESOLVED]
  • From: Rich Shepard
• Re: Syntax error needs explanation
  • From: David G. Johnston
• Re: Performance of JSON type in postgres
  • From: David G. Johnston
• Re: Syntax error needs explanation
  • From: Rich Shepard
• Re: Syntax error needs explanation
  • From: David G. Johnston
• Re: Performance of JSON type in postgres
  • From: Adrian Klaver
• Performance of JSON type in postgres
  • From: veem v
• Re: Syntax error needs explanation
  • From: Adrian Klaver
• Re: Syntax error needs explanation
  • From: Adrian Klaver
• Re: Syntax error needs explanation [RESOLVED]
  • From: Rich Shepard
• Re: Syntax error needs explanation
  • From: David G. Johnston
• Syntax error needs explanation
  • From: Rich Shepard
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Tom Lane
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: David G. Johnston
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Benjamin Wang
• Re: optimizing number of workers
  • From: Tom Lane
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Tom Lane
• Re: optimizing number of workers
  • From: Greg Hennessy
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Peter J. Holzer
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Laurenz Albe
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Tom Lane
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Laurenz Albe
• Re: Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Laurenz Albe
• Bypassing Directory Ownership Check in PostgreSQL 16.6 with Secure z/OS NFS (AT-TLS)
  • From: Amol Inamdar
• Re: I have a suspicious query
  • From: Ron Johnson
• Re: I have a suspicious query
  • From: Matthias Apitz
• Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication
  • From: Kiran K V
• Query regarding support of test_decoding and PGReplicationStream with Standby Logical Replication
  • From: Kiran K V
• Re: I have a suspicious query
  • From: Merlin Moncure
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Merlin Moncure
• Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: abrahim abrahao
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Adrian Klaver
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Merlin Moncure
• Re: I have a suspicious query
  • From: Greg Sabino Mullane
• Re: optimizing number of workers
  • From: Weck, Luis
• Re: I have a suspicious query
  • From: Adrian Klaver
• I have a suspicious query
  • From: Edmundo Robles
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Adrian Klaver
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Florents Tselai
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Adrian Klaver
• Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
  • From: Adrian Klaver
• Re: having temp_tablespaces on less reliable storage
  • From: Ron Johnson
• Re: having temp_tablespaces on less reliable storage
  • From: Dimitrios Apostolou
• Re: Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
  • From: Ron Johnson
• Question Regarding COPY Command Handling of Line Breaks in PostgreSQL
  • From: gzh
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Ron Johnson
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: Hayato Kuroda (Fujitsu)
• Re: Lock timeout in commit
  • From: Steve Baldwin
• optimizing number of workers
  • From: Greg Hennessy
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Merlin Moncure
• Re: having temp_tablespaces on less reliable storage
  • From: David G. Johnston
• having temp_tablespaces on less reliable storage
  • From: Dimitrios Apostolou
• Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: abrahim abrahao
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Ron Johnson
• Re: Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Adrian Klaver
• Re: analyze-in-stages post upgrade questions
  • From: Mircea Cadariu
• Re: Lock timeout in commit
  • From: Tom Lane
• Re: PostgresSQL Setup error
  • From: DINESH NAIR
• Lock timeout in commit
  • From: Steve Baldwin
• Aggregate versions of hashing functions (md5, sha1, etc...)
  • From: Dominique Devienne
• RE: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: Hayato Kuroda (Fujitsu)
• Re: Corrupt btree index includes rows that don't match
  • From: Peter Geoghegan
• Re: analyze-in-stages post upgrade questions
  • From: Laurenz Albe
• Re: Password Encryption and Connection Issues
  • From: Greg Sabino Mullane
• Re: Corrupt btree index includes rows that don't match
  • From: Erik Johnston
• Re: analyze-in-stages post upgrade questions
  • From: Mircea Cadariu
• Re: PostgresSQL Setup error
  • From: Adrian Klaver
• Re: PostgresSQL Setup error
  • From: Laurenz Albe
• PostgresSQL Setup error
  • From: Jordan Adams
• Re: Password Encryption and Connection Issues
  • From: Ron Johnson
• Re: Password Encryption and Connection Issues
  • From: Laurenz Albe
• Re: Password Encryption and Connection Issues
  • From: David G. Johnston
• Re: analyze-in-stages post upgrade questions
  • From: Laurenz Albe
• Re: Password Encryption and Connection Issues
  • From: Adrian Klaver
• Re: Password Encryption and Connection Issues
  • From: Ron Johnson
• Re: Password Encryption and Connection Issues
  • From: Ron Johnson
• Re: Password Encryption and Connection Issues
  • From: Greg Sabino Mullane
• Re: Password Encryption and Connection Issues
  • From: David G. Johnston
• Password Encryption and Connection Issues
  • From: Alpaslan AKDAĞ
• RE: analyze-in-stages post upgrade questions
  • From: Zechman, Derek S
• Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: Shlok Kyal
• Re: error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: Shlok Kyal
• error “server process was terminated by signal 11: Segmentation fault” running pg_create_logical_replication_slot using pgoutput plugin
  • From: abrahim abrahao
• Re: Logical Replication 08P01 invalid memory alloc request size 1095736448
  • From: Soni M
• Re: Logical Replication 08P01 invalid memory alloc request size 1095736448
  • From: Tom Lane
• Re: Logical Replication 08P01 invalid memory alloc request size 1095736448
  • From: Soni M
• Logical Replication 08P01 invalid memory alloc request size 1095736448
  • From: Soni M
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Pierre Fortin
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Adrian Klaver
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Adrian Klaver
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Adrian Klaver
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Ron Johnson
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Tom Lane
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Pierre Fortin
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Ron Johnson
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Tom Lane
• Re: pg_upgrade: can I use same binary for old & new?
  • From: pf
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Ron Johnson
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Adrian Klaver
• Re: pg_upgrade: can I use same binary for old & new?
  • From: pf
• Re: pg_upgrade: can I use same binary for old & new?
  • From: Tom Lane
• Re: pg_upgrade: can I use same binary for old & new?
  • From: David G. Johnston
• pg_upgrade: can I use same binary for old & new?
  • From: Pierre Fortin
• Re: Foreign Data Wrapper from Oracle to Postgres 16
  • From: DINESH NAIR
• Re: Corrupt btree index includes rows that don't match
  • From: Tom Lane
• Re: Corrupt btree index includes rows that don't match
  • From: Erik Johnston
• Re: Corrupt btree index includes rows that don't match
  • From: Ron Johnson
• Re: Corrupt btree index includes rows that don't match
  • From: Erik Johnston
• Re: Corrupt btree index includes rows that don't match
  • From: shammat
• Re: Corrupt btree index includes rows that don't match
  • From: Ron Johnson
• Re: Corrupt btree index includes rows that don't match
  • From: shammat
• Corrupt btree index includes rows that don't match
  • From: Erik Johnston
• Re: Foreign Data Wrapper from Oracle to Postgres 16
  • From: Laurenz Albe
• Foreign Data Wrapper from Oracle to Postgres 16
  • From: Santhosh S
• Re: PLPGSQL - store fetched records in array of record
  • From: Adrian Klaver
• Re: Postgresql support for Windows Server 2025
  • From: Laurenz Albe
• Re: Postgresql support for Windows Server 2025
  • From: Adrian Klaver
• Re: Postgresql support for Windows Server 2025
  • From: David G. Johnston
• Postgresql support for Windows Server 2025
  • From: Gaurav Aradhya
• Re: Simulate a PITR in postgresql 16
  • From: Franklin Anderson de Oliveira Souza
• Re: PLPGSQL - store fetched records in array of record
  • From: Durumdara
• Re: PLPGSQL - store fetched records in array of record
  • From: Ron Johnson
• Re: PLPGSQL - store fetched records in array of record
  • From: David G. Johnston
• PLPGSQL - store fetched records in array of record
  • From: Durumdara
• Fwd: Anomalous behavior between two Aurora Postgres RDS clusters
  • From: Amritanshu Joshi
• Re: The same query_id for different queries
  • From: Maksim Gorkov
• Re: The same query_id for different queries
  • From: Michael Paquier
• The same query_id for different queries
  • From: Maksim Gorkov
• Re: Simulate a PITR in postgresql 16
  • From: raphi
• Re: Simulate a PITR in postgresql 16
  • From: Christoph Moench-Tegeder
• Re: Simulate a PITR in postgresql 16
  • From: Adrian Klaver
• Re: Simulate a PITR in postgresql 16
  • From: Ron Johnson
• Simulate a PITR in postgresql 16
  • From: Franklin Anderson de Oliveira Souza
• LWLocks lock_manager occurences and timeouts
  • From: Sam Persoon
• Re: password rules
  • From: Peter J. Holzer
• Re: password rules
  • From: raphi
• Re: password rules
  • From: Ron Johnson
• Re: password rules
  • From: Peter J. Holzer
• Re: analyze-in-stages post upgrade questions
  • From: Laurenz Albe
• RE: analyze-in-stages post upgrade questions
  • From: Zechman, Derek S
• RE: analyze-in-stages post upgrade questions
  • From: Zechman, Derek S
• Re: analyze-in-stages post upgrade questions
  • From: Laurenz Albe
• Re: password rules
  • From: raphi
• Re: analyze-in-stages post upgrade questions
  • From: Adrian Klaver
• Re: Figure out nullability of query parameters
  • From: Greg Sabino Mullane
• Re: Figure out nullability of query parameters
  • From: David G. Johnston
• Re: Figure out nullability of query parameters
  • From: Petr Kada
• Figure out nullability of query parameters
  • From: Giacomo Cavalieri
• Re: analyze-in-stages post upgrade questions
  • From: Ron Johnson
• analyze-in-stages post upgrade questions
  • From: Zechman, Derek S
• Re: Question about different behaviour in pg_wal when archive_mode is set on or off
  • From: David G. Johnston
• Re: password rules
  • From: Peter J. Holzer
• Question about different behaviour in pg_wal when archive_mode is set on or off
  • From: Arpad Kiss A
• Re: password rules
  • From: raphi
• Re: password rules
  • From: Peter J. Holzer
• Re: PGPool II does not recognize backend_server0
  • From: Greg Sabino Mullane
• Re: password rules
  • From: raphi
• Re: password rules
  • From: Peter J. Holzer
• Re: Cannot turn track_counts on
  • From: Anton Shepelev
• Re: password rules
  • From: Greg Sabino Mullane
• Re: pg_combinebackup failure
  • From: Adrian Klaver
• Re: pg_combinebackup failure
  • From: Kouber Saparev
• Re: pg_combinebackup failure
  • From: Adrian Klaver
• Re: password rules
  • From: Gilles Darold
• PGPool II does not recognize backend_server0
  • From: Pablo Calientos
• pg_combinebackup failure
  • From: Kouber Saparev
• Re: IPC/MultixactCreation on the Standby server
  • From: Dmitry
• Re: password rules
  • From: raphi
• Re: postgres module in msvc
  • From: Adrian Klaver
• Re: password rules
  • From: Christoph Berg
• Re: postgres module in msvc
  • From: Adrian Klaver
• postgres module in msvc
  • From: C.
• Re: password rules
  • From: raphi
• Re: password rules
  • From: Tom Lane
• password rules
  • From: raphi
• IPC/MultixactCreation on the Standby server
  • From: Dmitry
• IPC/MultixactCreation on the Standby server
  • From: Dmitry
• Re: Extension disappearing act
  • From: Álvaro Herrera
• Re: PostgreSQL 17.5 - could not map dynamic shared memory segment
  • From: Aleš Zelený
• Memory overhead of a large number of partitions in the same table
  • From: César Muñoz
• Re: PostgreSQL 17.5 - could not map dynamic shared memory segment
  • From: Tomas Vondra
• PostgreSQL 17.5 - could not map dynamic shared memory segment
  • From: Aleš Zelený
• Re: Convert JSON value back to postgres representation
  • From: Phillip Diffley
• Re: Extension disappearing act
  • From: Adrian Klaver
• Re: Extension disappearing act
  • From: Merlin Moncure
• Re: undefined symbol: PQcancelStart
  • From: Peter Röthlisberger
• Re: undefined symbol: PQcancelStart
  • From: Laurenz Albe
• undefined symbol: PQcancelStart
  • From: Peter Röthlisberger
• Re: Retrieving current date
  • From: sivapostgres@xxxxxxxxx
• Re: Extension disappearing act
  • From: Tomas Vondra
• Re: Extension disappearing act
  • From: Dominique Devienne
• Re : does multi host connection string supports login event trigger exception
  • From: legrand legrand
• Re: Convert JSON value back to postgres representation
  • From: David G. Johnston
• Re: Convert JSON value back to postgres representation
  • From: Laurenz Albe
• Convert JSON value back to postgres representation
  • From: Phillip Diffley
• Re: does multi host connection string supports login event trigger exception
  • From: Pavel Luzanov
• does multi host connection string supports login event trigger exception
  • From: legrand legrand
• Re: Extension disappearing act
  • From: Laurenz Albe
• Re: Extension disappearing act
  • From: Dominique Devienne
• Re: Extension disappearing act
  • From: Tomas Vondra
• Re: Extension disappearing act
  • From: Adrian Klaver
• Re: Retrieving current date
  • From: Adrian Klaver
• Re: Retrieving current date
  • From: Ron Johnson
• Extension disappearing act
  • From: Dominique Devienne
• Re: Retrieving current date
  • From: David G. Johnston
• Re: Retrieving current date
  • From: sivapostgres@xxxxxxxxx
• Re: Postgres DB design Question (High Level)
  • From: Al Grant
• Re: Postgres DB design Question (High Level)
  • From: Laurenz Albe
• Postgres DB design Question (High Level)
  • From: Al Grant
• Request for Feedback on PostgreSQL HA + Load Balancing Architecture
  • From: vijay patil
• Re: Changing locale of an existing database
  • From: Marcin Gozdalik
• Re: Changing locale of an existing database
  • From: Adrian Klaver
• Re: Logical Replication Memory Allocation Error - "invalid memory alloc request size"
  • From: Masahiko Sawada
• Re: Changing locale of an existing database
  • From: Adrian Klaver
• Changing locale of an existing database
  • From: Marcin Gozdalik
• Re: Performance issues during pg_restore -j with big partitioned table
  • From: Dimitrios Apostolou
• Re: Stably escaping an identifier
  • From: Phillip Diffley
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: Adrian Klaver
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: David G. Johnston
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: Adrian Klaver
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: Richard Welty
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: Marco Torres
• Re: Getting error "too many clients already" despite having a db connection limit set
  • From: Tom Lane
• Getting error "too many clients already" despite having a db connection limit set
  • From: adolfo flores
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Rachel Roch
• Re: Stably escaping an identifier
  • From: Tom Lane
• Stably escaping an identifier
  • From: Phillip Diffley
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Adrian Klaver
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Adrian Klaver
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Rachel Roch
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Adrian Klaver
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Rachel Roch
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Adrian Klaver
• Re: pg_restore ERROR: permission denied to change default privileges
  • From: Tom Lane
• pg_restore ERROR: permission denied to change default privileges
  • From: Rachel Roch
• Re: db maintanance problem VACUUM FULL
  • From: Ron Johnson
• Re: db maintanance problem VACUUM FULL
  • From: Ron Johnson