pgsql-general  

Messages by Thread

• Questions about the continuity of WAL archiving px shi
  • Re: Questions about the continuity of WAL archiving Adrian Klaver
  • Re: Questions about the continuity of WAL archiving px shi
• Approach for DB migration Siraj G
  • Re: Approach for DB migration Ron Johnson
  • Re: Approach for DB migration Siraj G
  • Re: Approach for DB migration Ron Johnson
• CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters Pavel Stehule
  • Re: CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters David G. Johnston
  • Re: CALL and named parameters Pavel Stehule
  • Re: CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters Tom Lane
  • Re: CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters Tom Lane
  • Re: CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters Tom Lane
  • Re: CALL and named parameters Christoph Moench-Tegeder
  • Re: CALL and named parameters Tom Lane
  • Re: CALL and named parameters Dominique Devienne
  • Re: CALL and named parameters Adrian Klaver
  • Re: CALL and named parameters Christoph Moench-Tegeder
• Libpq.dll suport...@unitsistemas.com.br
  • Re: Libpq.dll Adrian Klaver
  • Re: Libpq.dll Merlin Moncure
• When UPDATE a row in a table with BEFORE ROW UPDATE trigger, the XMAX of new tuple is set to current XID 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 Adrian Klaver
• Stored procedures or raw queries Simon Connah
  • Re: Stored procedures or raw queries Pavel Stehule
  • Re: Stored procedures or raw queries Justin Swanhart
  • Re: Stored procedures or raw queries Dominique Devienne
  • Re: Stored procedures or raw queries Marco Torres
  • Re: Stored procedures or raw queries Philip Semanchuk
  • Re: Stored procedures or raw queries Simon Connah
• Notices not printed by PQtrace Dominique Devienne
  • Re: Notices not printed by PQtrace Álvaro Herrera
  • Re: Notices not printed by PQtrace Dominique Devienne
• PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený
  • Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený
  • Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený
  • Re: PGDG16 repository error - repomd.xml.asc is empty Adrian Klaver
  • Re: PGDG16 repository error - repomd.xml.asc is empty Aleš Zelený
• Inquiry: Using PostgreSQL as a Staging Database for SAP ERP Data Export Ian Huang
• What is the specific release date of PG18? 矫顺田
  • Re: What is the specific release date of PG18? David Rowley
  • Re: What is the specific release date of PG18? David G. Johnston
  • Re: What is the specific release date of PG18? David G. Johnston
• Re: Failing to allocate memory when I think it shouldn't Siraj G
  • Re: Failing to allocate memory when I think it shouldn't Christoph Moench-Tegeder
• SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Adrian Klaver
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Adrian Klaver
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Adrian Klaver
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Guillaume Lelarge
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Tom Lane
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Álvaro Herrera
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Adrian Klaver
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function David G. Johnston
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Adrian Klaver
  • Re: SET LOCAL ROLE inside SECURITY INVOKER (LANGUAGE plpgsql) function Dominique Devienne
• Can postgres replication slot using pgoutput release multiple CDC records for a single update to a particular row Akashkiran Shivakumar
• Get info about the index Igor Korot
  • Re: Get info about the index Adrian Klaver
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Christophe Pettus
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Laurenz Albe
  • Re: Get info about the index Jon Zeppieri
  • Re: Get info about the index David Barbour
  • Re: Get info about the index Laurenz Albe
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Laurenz Albe
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Laurenz Albe
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Adrian Klaver
  • Re: Get info about the index Igor Korot
  • Re: Get info about the index Adrian Klaver
  • Re: Get info about the index Jon Zeppieri
  • Re: Get info about the index Robert Sjöblom
  • Re: Get info about the index David G. Johnston
  • Re: Get info about the index Adrian Klaver
  • Re: Get info about the index Tom Lane
• PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Laurenz Albe
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Ron Johnson
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Rumpi Gravenstein
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array David G. Johnston
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Adrian Klaver
  • Re: PostgreSQL Bug with simple function unexpectedly treating varchar parameter as an array Tom Lane
• Upper / lower case keys in JSON objects Mark
  • Re: Upper / lower case keys in JSON objects Mark
  • Re: Upper / lower case keys in JSON objects Adrian Klaver
• Sorting by respecting diacritics/accents JānisE
  • Re: Sorting by respecting diacritics/accents Laurenz Albe
• Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Laurenz Albe
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Laurenz Albe
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command David Barbour
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
  • Re: Is there any limit on the number of rows to import using copy command Merlin Moncure
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
  • Re: Is there any limit on the number of rows to import using copy command sivapostg...@yahoo.com
  • Re: Is there any limit on the number of rows to import using copy command Ron Johnson
  • Re: Is there any limit on the number of rows to import using copy command Adrian Klaver
• Wrapping a select in another select makes it slower Peter J. Holzer
  • Re: Wrapping a select in another select makes it slower David Rowley
  • Re: Wrapping a select in another select makes it slower Peter J. Holzer
• Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU Klaus Darilion
  • Re: Postgresql 16.9 fast shutdown hangs with walsenders eating 100% CPU Laurenz Albe
• Possible causes of high_replay lag, given replication settings? Jon Zeppieri
  • Re: Possible causes of high_replay lag, given replication settings? Nick Cleaton
  • Re: Possible causes of high_replay lag, given replication settings? Jon Zeppieri
  • Re: Possible causes of high_replay lag, given replication settings? Greg Sabino Mullane
  • Re: Possible causes of high_replay lag, given replication settings? Jon Zeppieri
• PgBouncer Prepared Statement ERROR KK CHN
  • Re: PgBouncer Prepared Statement ERROR Greg Sabino Mullane
  • Re: PgBouncer Prepared Statement ERROR Laurenz Albe
  • Re: PgBouncer Prepared Statement ERROR Achilleas Mantzios
• Regarding logical replication issues with PostgreSQL versions 16 and above yexiu-glory
  • Re: Regarding logical replication issues with PostgreSQL versions 16 and above Laurenz Albe
  • Re: Regarding logical replication issues with PostgreSQL versions 16 and above DINESH NAIR
  • Re: Regarding logical replication issues with PostgreSQL versions 16and above yexiu-glory
  • Re: Regarding logical replication issues with PostgreSQL versions 16and above Laurenz Albe
• Should we document the cost of pg_database_size()? Alternatives? Craig Ringer
  • Re: Should we document the cost of pg_database_size()? Alternatives? Craig Ringer
  • Re: Should we document the cost of pg_database_size()? Alternatives? Ron Johnson
• PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Laurenz Albe
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Nico Williams
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Seref Arikan
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Vladimir Churyukin
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Vladimir Churyukin
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Seref Arikan
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Nico Williams
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Jeff Ross
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Marco Torres
  • Re: PostgreSQL on S3-backed Block Storage with Near-Local Performance Pierre Barre
• PgBouncer-Postgres : un supported startup parameter statement_timeout KK CHN
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Achilleas Mantzios
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Achilleas Mantzios
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Adrian Klaver
  • Re: PgBouncer-Postgres : un supported startup parameter statement_timeout Robert Sjöblom
• Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Jeff Ross
  • Re: Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Thom Brown
  • Re: Removing terminal period from varchar string in table column Rich Shepard
  • Re: Removing terminal period from varchar string in table column Thom Brown
  • Re: Removing terminal period from varchar string in table column Rich Shepard
• Regarding query optimisation (select for update) Durgamahesh Manne
  • Re: Regarding query optimisation (select for update) Laurenz Albe
  • Re: Regarding query optimisation (select for update) Durgamahesh Manne
  • Re: Regarding query optimisation (select for update) Laurenz Albe
  • Re: Regarding query optimisation (select for update) Tom Lane
  • Re: Regarding query optimisation (select for update) Greg Sabino Mullane
  • Re: Regarding query optimisation (select for update) Andy Huang
• Performance of JSON type in postgres veem v
  • Re: Performance of JSON type in postgres Adrian Klaver
  • Re: Performance of JSON type in postgres David G. Johnston
  • Re: Performance of JSON type in postgres Merlin Moncure
  • Re: Performance of JSON type in postgres veem v
  • Re: Performance of JSON type in postgres Adrian Klaver

• Earlier messages