Postgresql General Discussion

• Thread Index

• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Rob Sargent
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Ron
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Thomas Kellerer
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Ron
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Adrian Klaver
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Rob Sargent
• Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Ron
• ICU is not supported in this build. install from source code.
  • From: jian he
• Re: Strange collation names ("hu_HU.UTF-8")
  • From: Tom Lane
• Re: Syntax error when combining --set and --command has me stumped
  • From: Ron
• Re: Syntax error when combining --set and --command has me stumped
  • From: Gianni Ceccarelli
• Strange collation names ("hu_HU.UTF-8")
  • From: Durumdara
• Re: Creation of FK without enforcing constraint for existing data
  • From: Gavan Schneider
• Re: Creation of FK without enforcing constraint for existing data
  • From: sivapostgres@xxxxxxxxx
• Re: Inconsistent permission enforcement for schemas
  • From: Tom Lane
• Inconsistent permission enforcement for schemas
  • From: Marcin Barczyński
• Re: "set autocommit on" in golang client query
  • From: Guillaume Lelarge
• "set autocommit on" in golang client query
  • From: Rory Campbell-Lange
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: a database can be created but not droped
  • From: Frank Streitzig
• Re: a database can be created but not droped
  • From: Julien Rouhaud
• a database can be created but not droped
  • From: Matthias Apitz
• Is Client connections via ca.crt only possible?
  • From: Rejo Oommen
• Unable to start replica after failover
  • From: Lahnov, Igor
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: Adrian Klaver
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: Ron
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: Adrian Klaver
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: Tom Lane
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: Rob Sargent
• Connecting to postgres on OSX from Swift using PostgresClientKit
  • From: howardnews
• Re: Logical replication versus pglogical on PostgreSQL 14
  • From: Christian Barthel
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Bryn Llewellyn
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Pavel Stehule
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Bryn Llewellyn
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Christophe Pettus
• Re: Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Tom Lane
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Bryn Llewellyn
• Re: « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Christophe Pettus
• « The PL/pgSQL interpreter parses the function's source text and produces an internal binary instruction tree... »
  • From: Bryn Llewellyn
• Re: Syntax error when combining --set and --command has me stumped
  • From: Adrian Klaver
• Re: Syntax error when combining --set and --command has me stumped
  • From: Ron
• Re: Syntax error when combining --set and --command has me stumped
  • From: David G. Johnston
• Syntax error when combining --set and --command has me stumped
  • From: Ron
• Re: Was my question inappropriate for postgres?
  • From: Peter J. Holzer
• Re: Feature request(?): Proxy User
  • From: Alicja Kucharczyk
• Re: pg_dump query failed
  • From: Tom Lane
• Re: pg_dump query failed
  • From: Ron
• Re: Feature request(?): Proxy User
  • From: Mateusz Henicz
• Re: pg_dump query failed
  • From: David G. Johnston
• pg_dump query failed
  • From: karol . malinowski
• xmin of slot is not moving | hot standby feedback sending old xmin.
  • From: T T
• Feature request(?): Proxy User
  • From: Wiwwo Staff
• Re: Feature request: psql --idle
  • From: Wiwwo Staff
• Re:
  • From: Alicja Kucharczyk
• Re: Feature request: psql --idle
  • From: Michael Nolan
• Performance issue on GIN index with gin_trgm_ops index column
  • From: Lars Vonk
• Re: Feature request: psql --idle
  • From: Julien Rouhaud
• Re: Feature request: psql --idle
  • From: Mateusz Henicz
• Feature request: psql --idle
  • From: Wiwwo Staff
• monitor health of native logical replication
  • From: Rory Campbell-Lange
• Re:
  • From: hubert depesz lubaczewski
• Re:
  • From: Adrian Klaver
• Re:
  • From: Ron
• Re:
  • From: Adrian Klaver
• Re:
  • From: Rama Krishnan
• Re:
  • From: Adrian Klaver
• [no subject]
  • From: Rama Krishnan
• Re: Streaming Replication, can't select row in backup without specifying collation
  • From: Adrian Klaver
• Streaming Replication, can't select row in backup without specifying collation
  • From: Kelly Burkhart
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Alvaro Herrera
• Re: PL/pgSQL: « arr[j].a := v » works fine in PG Version 14.4, fails to compile in Version 11.2. Which version brought the fix?
  • From: Bryn Llewellyn
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Adrian Klaver
• Re: PL/pgSQL: « arr[j].a := v » works fine in PG Version 14.4, fails to compile in Version 11.2. Which version brought the fix?
  • From: David G. Johnston
• PL/pgSQL: « arr[j].a := v » works fine in PG Version 14.4, fails to compile in Version 11.2. Which version brought the fix?
  • From: Bryn Llewellyn
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Adrian Klaver
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Michael J. Baars
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Adrian Klaver
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Michael J. Baars
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Adrian Klaver
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Michael J. Baars
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Adrian Klaver
• Re: Was my question inappropriate for postgres?
  • From: Mladen Gogala
• Re: Password reset link / 'less' does not exit in psql version 13.4
  • From: Francisco Olarte
• Password reset link / 'less' does not exit in psql version 13.4
  • From: Michael J. Baars
• Re: Was my question inappropriate for postgres?
  • From: Alicja Kucharczyk
• Re: Was my question inappropriate for postgres?
  • From: Adrian Klaver
• Re: Was my question inappropriate for postgres?
  • From: Mladen Gogala
• Re: Was my question inappropriate for postgres?
  • From: Adrian Klaver
• Re: Was my question inappropriate for postgres?
  • From: Adrian Klaver
• Re: Was my question inappropriate for postgres?
  • From: Gavin Flower
• Re: Was my question inappropriate for postgres?
  • From: Gavin Flower
• Re: Was my question inappropriate for postgres?
  • From: Mladen Gogala
• Re: Was my question inappropriate for postgres?
  • From: Mladen Gogala
• Re: Was my question inappropriate for postgres?
  • From: Adrian Klaver
• Re: Was my question inappropriate for postgres?
  • From: Gavin Flower
• Re: Was my question inappropriate for postgres?
  • From: Adrian Klaver
• Was my question inappropriate for postgres?
  • From: Taka Taka
• Re: Queries in another user's tables (SOLVED)
  • From: xavier
• Re: Queries in another user's tables
  • From: Adrian Klaver
• Re: Strange behavior between timestamp and date comparison
  • From: Adrian Klaver
• Re: Strange behavior between timestamp and date comparison
  • From: Rory Campbell-Lange
• Strange behavior between timestamp and date comparison
  • From: Ludwig Isaac Lim
• Unable to archive logs in standby server
  • From: Meera Nair
• Re: Queries in another user's tables
  • From: Pavel Stehule
• Queries in another user's tables
  • From: xavier
• Re: Logging the query executed on the server
  • From: Steve Baldwin
• Re: Logging the query executed on the server
  • From: Igor Korot
• Re: Logging the query executed on the server
  • From: Steve Baldwin
• Logging the query executed on the server
  • From: Igor Korot
• Re: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Adrian Klaver
• Re: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Adrian Klaver
• Logical replication versus pglogical on PostgreSQL 14
  • From: Rory Campbell-Lange
• RE: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Techsupport
• Re: How does postgres sort large strings?
  • From: Francisco Olarte
• Re: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Adrian Klaver
• 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Techsupport
• How does postgres sort large strings?
  • From: Sergey Burladyan
• Re: Paging through table one row at a ttime
  • From: Bruce Momjian
• Re: Paging through table one row at a ttime
  • From: H
• Re: Paging through table one row at a ttime
  • From: Bruce Momjian
• Re: Paging through table one row at a ttime
  • From: Rob Sargent
• Re: Paging through table one row at a ttime
  • From: H
• Is psqlodbc_13_02 compatible to M365?
  • From: Taka Taka
• Re: could not link file in wal restore lines
  • From: Zsolt Ero
• Re: FK Constraint sort order with pg_dump
  • From: Tom Lane
• Re: FK Constraint sort order with pg_dump
  • From: Adrian Klaver
• Re: FK Constraint sort order with pg_dump
  • From: Christian Barthel
• Re: FK Constraint sort order with pg_dump
  • From: David G. Johnston
• Re: FK Constraint sort order with pg_dump
  • From: Adrian Klaver
• FK Constraint sort order with pg_dump
  • From: Christian Barthel
• Re: Unable to archive logs in standby server
  • From: Guillaume Lelarge
• Unable to archive logs in standby server
  • From: Meera Nair
• RE: [External]Re: Patroni & PostgreSQL issue
  • From: Menon, Deepak (Deepak)
• Re: More than one Cluster on single server (single instance)
  • From: Daulat
• Re: plan for function returning table combined with condition
  • From: Thierry Henrio
• Re: More than one Cluster on single server (single instance)
  • From: Daulat
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: postgis
  • From: Marc Millas
• Re: Patroni & PostgreSQL issue
  • From: Abdul Sayeed
• Re: Batch process
  • From: Adrian Klaver
• Re: Batch process
  • From: Ron
• Re: plan for function returning table combined with condition
  • From: Tom Lane
• Re: Batch process
  • From: Adrian Klaver
• Re: Batch process
  • From: Ron
• plan for function returning table combined with condition
  • From: Thierry Henrio
• Re: Batch process
  • From: Adrian Klaver
• Re: postgis
  • From: Imre Samu
• Re: postgis
  • From: David G. Johnston
• Re: postgis
  • From: David G. Johnston
• Re: postgis
  • From: Imre Samu
• Re: postgis
  • From: Adrian Klaver
• Re: postgis
  • From: Adrian Klaver
• Re: postgis
  • From: David G. Johnston
• Re: postgis
  • From: Adrian Klaver
• Re: Batch process
  • From: Rob Sargent
• Re: Batch process
  • From: Rama Krishnan
• Re: Batch process
  • From: Adrian Klaver
• Re: postgis
  • From: David G. Johnston
• Re: Batch process
  • From: Adrian Klaver
• Re: postgis
  • From: Marc Millas
• Re: postgis
  • From: jian he
• Re: postgis
  • From: Marc Millas
• Re: operator does not exist: text = bytea
  • From: Tom Lane
• Re: postgis
  • From: Ron
• Re: postgis
  • From: Marc Millas
• Paging through table one row at a ttime
  • From: H
• Re: operator does not exist: text = bytea
  • From: Karthik K L V
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• Re: operator does not exist: text = bytea
  • From: hubert depesz lubaczewski
• Patroni & PostgreSQL issue
  • From: Sankar, Uma (Uma)
• Re: operator does not exist: text = bytea
  • From: Karthik K L V
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Karsten Hilbert
• operator does not exist: text = bytea
  • From: Karthik K L V
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Sebastien Flaesch
• Re: Batch process
  • From: Ron
• Re: postgis
  • From: Ron
• RE: Proposed Translations of Updated Code of Conduct Policy
  • From: Lucie Šimečková
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Francisco Olarte
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Thomas Kellerer
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Sebastien Flaesch
• Re: Migrating from Oracle - Implicit Casting Issue
  • From: Karthik K L V
• Batch process
  • From: Rama Krishnan
• Re: postgis
  • From: Marc Millas
• Re: citext on exclude using gist
  • From: David G. Johnston
• Re: postgis
  • From: Imre Samu
• Re: citext on exclude using gist
  • From: Tom Lane
• citext on exclude using gist
  • From: Jean Carlo Giambastiani Lopes
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Gavan Schneider
• Re: postgis
  • From: Adrian Klaver
• Re: postgis
  • From: Marc Millas
• Re: postgis
  • From: Adrian Klaver
• Re: postgis
  • From: Marc Millas
• Re: postgis
  • From: Marc Millas
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Francisco Olarte
• Re: Out Of Memory
  • From: Adrian Klaver
• Re: Out Of Memory
  • From: Adrian Klaver
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Adrian Klaver
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Adrian Klaver
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Adrian Klaver
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: David G. Johnston
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• Re: restore question
  • From: Ronald Haynes
• Re: postgis
  • From: Imre Samu
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• Re: postgis
  • From: Adrian Klaver
• Re: restore question
  • From: Adrian Klaver
• Re: postgis
  • From: Marc Millas
• Re: restore question
  • From: Adrian Klaver
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Sebastien Flaesch
• Re: restore question
  • From: Benedict Holland
• Re: restore question
  • From: Ronald Haynes
• Re: postgis
  • From: Adrian Klaver
• Re: Getting the table ID
  • From: Igor Korot
• Re: About limitation of using postgresql in china
  • From: jian he
• Re: postgis
  • From: Marc Millas
• Re: Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Tom Lane
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Adrian Klaver
• Concurrent INSERT statements with RETURNING clause resetting SERIAL sequence
  • From: Sebastien Flaesch
• Re: How to handle failed COMMIT
  • From: Håvar Nøvik
• Re: Setting up a server with previous day data
  • From: Adrian Klaver
• Re: Out Of Memory
  • From: Adrian Klaver
• Re: How to handle failed COMMIT
  • From: David G. Johnston
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Tom Lane
• Re: pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: David G. Johnston
• Re: How to handle failed COMMIT
  • From: David G. Johnston
• Re: About limitation of using postgresql in china
  • From: Tom Lane
• Out Of Memory
  • From: ghoostinger
• RE: pg_dump is filling C: drive up to 100 percent
  • From: Meera Nair
• Re: restore question
  • From: Ray O'Donnell
• Re: postgis
  • From: Mladen Gogala
• Re: pg_dump is filling C: drive up to 100 percent
  • From: Thomas Boussekey
• RE: pg_dump is filling C: drive up to 100 percent
  • From: Meera Nair
• pgsql 10.19 : "ERROR: cannot convert infinity to numeric" except there is no infinity
  • From: Achilleas Mantzios
• restore question
  • From: Ronald Haynes
• Re: pg_dump is filling C: drive up to 100 percent
  • From: Abdul Qoyyuum
• Re: Setting up a server with previous day data
  • From: Abdul Qoyyuum
• Re: Getting the table ID
  • From: Walter Dörwald
• About limitation of using postgresql in china
  • From: pig lee
• Re: pg_receivewal/xlog to ship wal to cloud
  • From: Ganesh Korde
• pg_dump is filling C: drive up to 100 percent
  • From: Meera Nair
• How to handle failed COMMIT
  • From: Håvar Nøvik
• Setting up a server with previous day data
  • From: Srinivasa T N
• Re: Proposed Translations of Updated Code of Conduct Policy
  • From: Guillaume Lelarge
• Re: Proposed Translations of Updated Code of Conduct Policy
  • From: Stefan Fercot
• Migrating from Oracle - Implicit Casting Issue
  • From: David G. Johnston
• Migrating from Oracle - Implicit Casting Issue
  • From: Karthik K L V
• Re: equivalent thing of mtr in mysql
  • From: Christophe Pettus
• Re: Getting the table ID
  • From: David G. Johnston
• Getting the table ID
  • From: Igor Korot
• Re: equivalent thing of mtr in mysql
  • From: merryok
• Re: postgis
  • From: Adrian Klaver
• Re: pg_receivewal/xlog to ship wal to cloud
  • From: Alan Hodgson
• Re: pg_receivewal/xlog to ship wal to cloud
  • From: neslişah demirci
• pg_receivewal/xlog to ship wal to cloud
  • From: neslişah demirci
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Tom Lane
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Pavel Stehule
• Re: postgis
  • From: Marc Millas
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: postgis
  • From: Adrian Klaver
• Re: postgis
  • From: Adrian Klaver
• postgis
  • From: Marc Millas
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Tom Lane
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: More than one Cluster on single server (single instance)
  • From: Ron
• Re: More than one Cluster on single server (single instance)
  • From: Ron
• Re: More than one Cluster on single server (single instance)
  • From: Mladen Gogala
• Re: More than one Cluster on single server (single instance)
  • From: Guillaume Lelarge
• More than one Cluster on single server (single instance)
  • From: Daulat
• Re: Oracle to Postgress Migration
  • From: Gogala, Mladen
• Proposed Translations of Updated Code of Conduct Policy
  • From: Lucie Šimečková
• Re: Error when pasting function blocks into psql
  • From: Ludwig Isaac Lim
• Re: Proposal to introduce a shuffle function to intarray extension
  • From: Mladen Gogala
• Re: Proposal to introduce a shuffle function to intarray extension
  • From: Martin Kalcher
• Re: Proposal to introduce a shuffle function to intarray extension
  • From: Mladen Gogala
• Re: equivalent thing of mtr in mysql
  • From: Adrian Klaver
• Re:Re: equivalent thing of mtr in mysql
  • From: merryok
• could not link file in wal restore lines
  • From: Zsolt Ero
• Re: About revoking large number of privileges; And the PUBLIC role.
  • From: Stephen Frost
• Proposal to introduce a shuffle function to intarray extension
  • From: Martin Kalcher
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Tomas Vondra
• Re: Oracle to Postgress Migration
  • From: DAVID ROTH
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Pavel Stehule
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: Oracle to Postgress Migration
  • From: Bruce Momjian
• Oracle to Postgress Migration
  • From: DAVID ROTH
• Re: first order by then partition by x < a fixed value.
  • From: Frank Streitzig
• first order by then partition by x < a fixed value.
  • From: jian he
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Issues with upserts
  • From: Adrian Klaver
• Re: Issues with upserts
  • From: David G. Johnston
• Re: Issues with upserts
  • From: Tom Lane
• RE: Issues with upserts
  • From: André Hänsel
• Re: Issues with upserts
  • From: David G. Johnston
• Re: Issues with upserts
  • From: Jeremy Smith
• Issues with upserts
  • From: André Hänsel
• Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Ken Yeung
• Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Laurenz Albe
• Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Ken Yeung
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Michael Paquier
• Re: equivalent thing of mtr in mysql
  • From: Peter J. Holzer
• Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Laurenz Albe
• Re: equivalent thing of mtr in mysql
  • From: Rob Sargent
• Re: equivalent thing of mtr in mysql
  • From: Peter J. Holzer
• equivalent thing of mtr in mysql
  • From: merryok
• Re: Get the table creation DDL
  • From: Rob Sargent
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Thomas Boussekey
• Re: - operator overloading not giving expected result
  • From: Rajesh S
• Problem upgrading from 10 to 14 with pg_upgrade: unexpected error upgrading "template1" database for some clusters
  • From: Ken Yeung
• Is there a official benchmark comparing PG versions?
  • From: Jean Baro
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: Get the table creation DDL
  • From: Rob Sargent
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Pavel Stehule
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Rob Sargent
• PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: Get the table creation DDL
  • From: Walter Dörwald
• Re: Get the table creation DDL
  • From: Rob Sargent
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Rob Sargent
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Mladen Gogala
• Re: Get the table creation DDL
  • From: Michael Nolan
• Re: Get the table creation DDL
  • From: Ray O'Donnell
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Igor Korot
• Re: Get the table creation DDL
  • From: Michael Nolan
• Get the table creation DDL
  • From: Igor Korot
• Re: range with infinity bound data type disallow extra empty white space.
  • From: David G. Johnston
• range with infinity bound data type disallow extra empty white space.
  • From: jian he
• Re: Database designs
  • From: Josef Šimánek
• Re: Database designs
  • From: Pete Yunker
• Re: Database designs
  • From: Josef Šimánek
• Re: Database designs
  • From: Pete Yunker
• Database designs
  • From: Zahid Rahman
• Re: - operator overloading not giving expected result
  • From: Ravi Krishna
• Re: Error when pasting function blocks into psql
  • From: Tom Lane
• Re: - operator overloading not giving expected result
  • From: Tom Lane
• Re: - operator overloading not giving expected result
  • From: Christoph Moench-Tegeder
• Re: - operator overloading not giving expected result
  • From: Francisco Olarte
• Re: CPU is 100% azure rds postgreSQL-11
  • From: Sunil Thakur
• Re: Error when pasting function blocks into psql
  • From: Francisco Olarte
• Re: postgresql bug
  • From: Christoph Moench-Tegeder
• Re: postgresql generate ddl returns FK with `<?>()` in it
  • From: Francisco Olarte
• Re: postgresql generate ddl returns FK with `<?>()` in it
  • From: Peter J. Holzer
• Re: postgresql bug
  • From: Laurenz Albe
• Re: - operator overloading not giving expected result
  • From: Peter J. Holzer
• postgresql bug
  • From: ml
• CPU is 100% azure rds postgreSQL-11
  • From: Pavan Kumar S
• Why does pg_statio_user_tables report heap_blks_hit after index only scan?
  • From: Aleksander Łukasz
• Error when pasting function blocks into psql
  • From: Ludwig Isaac Lim
• postgresql generate ddl returns FK with `<?>()` in it
  • From: Roman Gavrilov
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• - operator overloading not giving expected result
  • From: Rajesh S
• Re: About revoking large number of privileges; And the PUBLIC role.
  • From: Peter J. Holzer
• Re: Seems to be impossible to set a NULL search_path
  • From: Peter J. Holzer
• Re: About revoking large number of privileges; And the PUBLIC role.
  • From: Laurenz Albe
• Re: About revoking large number of privileges; And the PUBLIC role.
  • From: Dominique Devienne
• Re: About revoking large number of privileges; And the PUBLIC role.
  • From: Tom Lane
• About revoking large number of privileges; And the PUBLIC role.
  • From: Dominique Devienne
• Re: database designs ERDs
  • From: Zahid Rahman
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: Rob Sargent
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: lifetime of the old CTID
  • From: Adrian Klaver
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: lifetime of the old CTID
  • From: Christophe Pettus
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: lifetime of the old CTID
  • From: Ron
• Re: Multiple Indexes
  • From: David Rowley
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: lifetime of the old CTID
  • From: Karsten Hilbert
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: Seems to be impossible to set a NULL search_path
  • From: Christophe Pettus
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Multiple Indexes
  • From: DAVID ROTH
• Re: lifetime of the old CTID
  • From: Ilya Anfimov
• Re: Seems to be impossible to set a NULL search_path
  • From: Adrian Klaver
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Francisco Olarte
• Re: lifetime of the old CTID
  • From: Peter J. Holzer
• Re: lifetime of the old CTID
  • From: Alvaro Herrera
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Alvaro Herrera
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Florents Tselai
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Florents Tselai
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Francisco Olarte
• Re: unable to understand query result
  • From: Stefan Froehlich
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Florents Tselai
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Florents Tselai
• Re: lifetime of the old CTID
  • From: Karsten Hilbert
• Re: lifetime of the old CTID
  • From: Karsten Hilbert
• Re: unable to understand query result
  • From: Peter Eisentraut
• Re: ADD COLUMN ts tsvector GENERATED too slow
  • From: Peter Eisentraut
• unable to understand query result
  • From: Stefan Froehlich
• ADD COLUMN ts tsvector GENERATED too slow
  • From: Florents Tselai
• Re: How to upgrade postgres version 8 to 13
  • From: Laurenz Albe
• Re: lifetime of the old CTID
  • From: Laurenz Albe
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: lifetime of the old CTID
  • From: Andreas Kretschmer
• Re: lifetime of the old CTID
  • From: Andreas Kretschmer
• Re: lifetime of the old CTID
  • From: Christophe Pettus
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• RE: General Inquiry
  • From: Cloete, F. (Francois)
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: How to upgrade postgres version 8 to 13
  • From: shashidhar Reddy
• Re: Seems to be impossible to set a NULL search_path
  • From: David G. Johnston
• Re: General Inquiry
  • From: Kyotaro Horiguchi
• Re: Seems to be impossible to set a NULL search_path
  • From: Adrian Klaver
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: Seems to be impossible to set a NULL search_path
  • From: Tom Lane
• Re: Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: How to upgrade postgres version 8 to 13
  • From: Michael Nolan
• Re: Seems to be impossible to set a NULL search_path
  • From: Adrian Klaver
• Re: Seems to be impossible to set a NULL search_path
  • From: Pavel Stehule
• Re: Seems to be impossible to set a NULL search_path
  • From: Christophe Pettus
• Re: Seems to be impossible to set a NULL search_path
  • From: Adrian Klaver
• Re: How to upgrade postgres version 8 to 13
  • From: David G. Johnston
• Seems to be impossible to set a NULL search_path
  • From: Bryn Llewellyn
• Re: How to upgrade postgres version 8 to 13
  • From: Adrian Klaver
• Re: How to upgrade postgres version 8 to 13
  • From: shashidhar Reddy
• Re: How to upgrade postgres version 8 to 13
  • From: Adrian Klaver
• Re: How to upgrade postgres version 8 to 13
  • From: Adrian Klaver
• How to upgrade postgres version 8 to 13
  • From: shashidhar Reddy
• Re: lifetime of the old CTID
  • From: Laurenz Albe
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: lifetime of the old CTID
  • From: Laurenz Albe
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: lifetime of the old CTID
  • From: Matthias Apitz
• Re: General Inquiry
  • From: Tim Clarke
• General Inquiry
  • From: Cloete, F. (Francois)
• Re: lifetime of the old CTID
  • From: Laurenz Albe
• lifetime of the old CTID
  • From: Matthias Apitz
• Re: Getting data from a record variable dynamically
  • From: Alban Hertroys
• Re: Getting data from a record variable dynamically
  • From: David G. Johnston
• Getting data from a record variable dynamically
  • From: Rhys A.D. Stewart
• Re: AIX and EAGAIN on open()
  • From: Christoph Berg
• Postgresql 13.7 hangs down
  • From: Bogdan Siara
• Re: Beginner Question:Why it always make sure that the postgres better than common csv file storage in disaster recovery?
  • From: Tom Lane
• Re: Beginner Question:Why it always make sure that the postgres better than common csv file storage in disaster recovery?
  • From: Adrian Klaver
• Beginner Question:Why it always make sure that the postgres better than common csv file storage in disaster recovery?
  • From: Wen Yi
• Re: AIX and EAGAIN on open()
  • From: Thomas Munro
• Re: plpgsql_check issue while upgrading from postgres version 12 to 13.7
  • From: Pavel Stehule
• plpgsql_check issue while upgrading from postgres version 12 to 13.7
  • From: shashidhar Reddy
• Re: Libpq question related to allocated resources
  • From: Karl Denninger
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Bryn Llewellyn
• Re: Function inside query status
  • From: Adrian Klaver
• Re: Fatel: unsupported frientend protocol error
  • From: Tom Lane
• pg_amcheck warnings after upgrade to 14.4
  • From: Aleš Zelený
• Re: Fatel: unsupported frientend protocol error
  • From: David G. Johnston
• Re: Fatel: unsupported frientend protocol error
  • From: Laurenz Albe
• Fatel: unsupported frientend protocol error
  • From: eswar reddy
• Function inside query status
  • From: Rama Krishnan
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: David G. Johnston
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Bryn Llewellyn
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: David G. Johnston
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Bryn Llewellyn
• Question on pg_auto_failover extension
  • From: DAN LU
• RE: help for pg_wal issue
  • From: Özge Özyavuz
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Christophe Pettus
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Pavel Stehule
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Laurenz Albe
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Tom Lane
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Pavel Stehule
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Tom Lane
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: David G. Johnston
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Pavel Stehule
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Bryn Llewellyn
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: David G. Johnston
• Re: User's responsibility when using a chain of "immutable" functions?
  • From: Christophe Pettus
• User's responsibility when using a chain of "immutable" functions?
  • From: Bryn Llewellyn
• Re: Unique index prohibits partial aggregates
  • From: David Rowley
• RE: Unique index prohibits partial aggregates
  • From: Bos, Fred
• Re: Libpq question related to allocated resources
  • From: Karl Denninger
• GIN index operator ?(jsonb,text) not working?
  • From: jian he
• Re: help for pg_wal issue
  • From: Kyotaro Horiguchi
• Re: help for pg_wal issue
  • From: Kyotaro Horiguchi
• Re:Re: Different sort result between PostgreSQL 8.4 and 12.5
  • From: gzh
• Re: Libpq question related to allocated resources
  • From: Tom Lane
• Re: Unique index prohibits partial aggregates
  • From: David Rowley
• Re: Outer joins and NULLs (old subject "ERROR: failed to find conversion function from key_vals_nn to record[]")
  • From: Bryn Llewellyn
• Libpq question related to allocated resources
  • From: Karl Denninger
• Re: Table space not returned to the OS ?
  • From: Magnus Hagander
• Unique index prohibits partial aggregates
  • From: Bos, Fred
• Re: Different sort result between PostgreSQL 8.4 and 12.5
  • From: Magnus Hagander
• Different sort result between PostgreSQL 8.4 and 12.5
  • From: gzh
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: Wolfgang Rißler
• Re: Question about attention to pgsql-hackers@xxxxxxxxxxxxxxxxxxxx
  • From: Imre Samu
• Re: help for pg_wal issue
  • From: Laurenz Albe
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: Daniel Verite
• help for pg_wal issue
  • From: Özge Özyavuz
• Re: Table space not returned to the OS ?
  • From: Laurenz Albe
• Re: Table space not returned to the OS ?
  • From: Florents Tselai
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: Wolfgang Rißler
• Re: Table space not returned to the OS ?
  • From: Thomas Boussekey
• Re: Table space not returned to the OS ?
  • From: Magnus Hagander
• Table space not returned to the OS ?
  • From: Florents Tselai
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: David G. Johnston
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: WR
• Sv: How can I set up Postgres to use given amount of RAM?
  • From: Andreas Joseph Krogh
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: WR
• Re: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Michael Paquier
• Re: How can I set up Postgres to use given amount of RAM?
  • From: Mladen Gogala
• Re: How can I set up Postgres to use given amount of RAM?
  • From: Zahid Rahman
• How can I set up Postgres to use given amount of RAM?
  • From: W.P.
• Re: Question about attention to pgsql-hackers@xxxxxxxxxxxxxxxxxxxx
  • From: Mladen Gogala
• Re: Question about attention to pgsql-hackers@xxxxxxxxxxxxxxxxxxxx
  • From: Julien Rouhaud
• Re: Question about attention to pgsql-hackers@xxxxxxxxxxxxxxxxxxxx
  • From: Laurenz Albe
• Question about attention to pgsql-hackers@xxxxxxxxxxxxxxxxxxxx
  • From: A Z
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Peter J. Holzer
• Re: Automatic autovacuum to prevent wraparound - PG13.5
  • From: Peter Geoghegan
• Re: Automatic autovacuum to prevent wraparound - PG13.5
  • From: Ninad Shah
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tom Lane
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Peter Eisentraut
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tomas Pospisek
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: Daniel Verite
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Adrian Klaver
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Adrian Klaver
• Re: Differences in Escaped bytea's when creating a plain pg_dump
  • From: WR
• Differences in Escaped bytea's when creating a plain pg_dump
  • From: WR
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tomas Pospisek
• Re: INSERT ALL with DML ERROR Logging replacement in PostgreSQL
  • From: Jagmohan Kaintura
• Re: function currtid2() in SQL and ESQL/C to get the new CTID of a row
  • From: Matthias Apitz
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Jeff Janes
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Jeff Janes
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tom Lane
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Tom Lane
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Peter J. Holzer
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Peter J. Holzer
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Peter J. Holzer
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Peter J. Holzer
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tomas Pospisek
• Re: Tuning a query with ORDER BY and LIMIT
  • From: Michael van der Kolff
• Tuning a query with ORDER BY and LIMIT
  • From: Dirschel, Steve
• Re: ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Adrian Klaver
• ERROR: new collation (en_US.UTF-8) is incompatible with the collation of the template database (en_US.utf-8)
  • From: Tomas Pospisek
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• PostgreSQL with Patroni not replicating to all nodes after adding 3rd node (another secondary)
  • From: Zb B
• RE: How to use 32 bit ODBC driver
  • From: Aditya Bhardwaj
• Source code test data folder don't have CSV files. How to get the CSV file.
  • From: jian he
• Re: function currtid2() in SQL and ESQL/C to get the new CTID of a row
  • From: Matthias Apitz
• Re: How to use 32 bit ODBC driver
  • From: Adrian Klaver
• Re: How to use 32 bit ODBC driver
  • From: Rino Mardo
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• How to use 32 bit ODBC driver
  • From: Aditya Bhardwaj
• Re: accessing postgres from c++
  • From: Rino Mardo
• Re: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mateusz Henicz
• Reminder: Call for Papers for PostgreSQL Conference Europe 2022 is closing soon!
  • From: Andreas 'ads' Scherbaum
• Re: INSERT ALL with DML ERROR Logging replacement in PostgreSQL
  • From: Gilles Darold
• Re: INSERT ALL with DML ERROR Logging replacement in PostgreSQL
  • From: Jagmohan Kaintura
• Re: accessing postgres from c++
  • From: Matthias Apitz
• Re: INSERT ALL with DML ERROR Logging replacement in PostgreSQL
  • From: Gilles Darold
• INSERT ALL with DML ERROR Logging replacement in PostgreSQL
  • From: Jagmohan Kaintura
• Re: accessing postgres from c++
  • From: Dominique Devienne
• Re: accessing postgres from c++
  • From: Laurenz Albe
• Re: Index creation
  • From: Дмитрий Иванов
• accessing postgres from c++
  • From: Rino Mardo
• Re: A error happend when I am clone the git repository
  • From: Magnus Hagander
• Re: Index creation
  • From: Jeff Janes
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• AIX and EAGAIN on open()
  • From: Christoph Berg
• Re: Index creation
  • From: Дмитрий Иванов
• Re: A error happend when I am clone the git repository
  • From: Tom Lane
• Re: A error happend when I am clone the git repository
  • From: Adrian Klaver
• A error happend when I am clone the git repository
  • From: Wen Yi
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Re: Outer joins and NULLs (old subject "ERROR: failed to find conversion function from key_vals_nn to record[]")
  • From: David G. Johnston
• Re: Outer joins and NULLs (old subject "ERROR: failed to find conversion function from key_vals_nn to record[]")
  • From: Tom Lane
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Thomas Kellerer
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Outer joins and NULLs (old subject "ERROR: failed to find conversion function from key_vals_nn to record[]")
  • From: Bryn Llewellyn
• Re: Index creation
  • From: David G. Johnston
• Index creation
  • From: Дмитрий Иванов
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: jian he
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Re: ISBN (was: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?)
  • From: Bryn Llewellyn
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Alban Hertroys
• Re:
  • From: Peter J. Holzer
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Peter J. Holzer
• ISBN (was: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?)
  • From: Peter J. Holzer
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type
  • From: Pavel Stehule
• Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type
  • From: Daniel Popowich
• RE: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• Re: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Laurenz Albe
• Re: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mateusz Henicz
• Re: Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mateusz Henicz
• Postgresql error : PANIC: could not locate a valid checkpoint record
  • From: Mahendrakar, Prabhakar - Dell Team
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Bryn Llewellyn
• Re: Any way to understand state after data corruption failures during startup.
  • From: Kyotaro Horiguchi
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: David G. Johnston
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Bryn Llewellyn
• Any way to understand state after data corruption failures during startup.
  • From: Harinath Kanchu
• Re:
  • From: Abdul Qoyyuum
• Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type
  • From: Bryn Llewellyn
• Re: Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type
  • From: Tom Lane
• Operators on ranges with a domain subtype do not implicitly cast operands of the domain's base type
  • From: Daniel Popowich
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Tom Lane
• Re:
  • From: Adrian Klaver
• [no subject]
  • From: Rama Krishnan
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: David G. Johnston
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Bryn Llewellyn
• Re: ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: David G. Johnston
• ERROR: failed to find conversion function from key_vals_nn to record[]
  • From: Bryn Llewellyn
• Re: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Imre Samu
• Re: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Adrian Klaver
• Re: Recent 11.16 release change
  • From: Daniel Brinzila
• Re: Automatic autovacuum to prevent wraparound - PG13.5
  • From: Laurenz Albe
• Re: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Tom Lane
• Re: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Ray O'Donnell
• Automatic autovacuum to prevent wraparound - PG13.5
  • From: Mauro Farracha
• RE: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Ian Dauncey
• Re: PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Ray O'Donnell
• PostgreSQL 12.2 on Linux ubuntu 20.4 / s390
  • From: Ian Dauncey
• Re: cast to domain with default collation issue.
  • From: Tom Lane
• Re: Recent 11.16 release change
  • From: Tom Lane
• Recent 11.16 release change
  • From: Daniel Brinzila
• Re: Postgres NOT IN vs NOT EXISTS optimization
  • From: Tom Lane
• Re: Postgres NOT IN vs NOT EXISTS optimization
  • From: Jeremy Smith
• Postgres NOT IN vs NOT EXISTS optimization
  • From: Dirschel, Steve
• Re: Tools to convert timestamp data to another time zone in PostgreSQL
  • From: Ilya Anfimov
• RE: Build Postgres On AIX
  • From: Mark Hill
• Re: multiple entries for synchronous_standby_names
  • From: Michael Paquier
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Bryn Llewellyn
• Re: Tools to convert timestamp data to another time zone in PostgreSQL
  • From: Adrian Klaver
• Tools to convert timestamp data to another time zone in PostgreSQL
  • From: Joel Rabinovitch
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Christophe Pettus
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Pavel Stehule
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Tom Lane
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Bryn Llewellyn
• Re: Need optimization in query
  • From: Shubham Mittal
• Re: "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Pavel Stehule
• "A block containing an EXCEPTION clause is significantly more expensive to enter and exit than a block without one"
  • From: Bryn Llewellyn
• Re: newbie db design question
  • From: Rino Mardo
• Re: PG_GETARG_TEXT_PP vs PG_GETARG_TEXT_P
  • From: Tom Lane
• Re: PG_GETARG_TEXT_PP vs PG_GETARG_TEXT_P
  • From: Markur Sens
• Re: PG_GETARG_TEXT_PP vs PG_GETARG_TEXT_P
  • From: Tom Lane
• PG_GETARG_TEXT_PP vs PG_GETARG_TEXT_P
  • From: Markur Sens
• multiple entries for synchronous_standby_names
  • From: Nitesh Nathani
• Re: newbie db design question
  • From: Peter J. Holzer
• Re: newbie db design question
  • From: Ray O'Donnell
• Re: newbie db design question
  • From: Gavan Schneider
• newbie db design question
  • From: Rino Mardo
• Re: How to drop a subscription inside a stored procedure?
  • From: Thomas Kellerer
• Need optimization in query
  • From: Shubham Mittal
• Re: How to get response message
  • From: David G. Johnston
• Re: How to get response message
  • From: Francisco Olarte
• Re: How to get response message
  • From: Adrian Klaver
• How to get response message
  • From: Rama Krishnan
• Re: How to drop a subscription inside a stored procedure?
  • From: Adrian Klaver
• How to drop a subscription inside a stored procedure?
  • From: Thomas Kellerer
• Re: Row level security insert policy does not validate update new values/content?
  • From: David G. Johnston
• Re: cast to domain with default collation issue.
  • From: David G. Johnston
• Re: Logical replication of large objects
  • From: Andreas Joseph Krogh
• Re: Logical replication of large objects
  • From: Joshua Drake
• Re: Sharing DSA pointer between parallel workers after they've been created
  • From: Joshua Drake
• Re: Cluster OID Limit
  • From: Joshua Drake
• Re: Cluster OID Limit
  • From: SERHAD ERDEM
• Re: Cluster OID Limit
  • From: Adrian Klaver
• Re: Cluster OID Limit
  • From: Tom Lane
• A function to find errors in groups in a table
  • From: Shaozhong SHI
• Cluster OID Limit
  • From: Lucas
• Re: message log merge (streaming replication)
  • From: Kyotaro Horiguchi
• Re: message log merge (streaming replication)
  • From: Ian Lawrence Barwick
• Fwd: message log merge (streaming replication)
  • From: Peter Adlersburg
• Sharing DSA pointer between parallel workers after they've been created
  • From: Ma, Marcus
• Re: FATAL: could not receive timeline history file from the primary server: ERROR: could not open file "pg_wal/0000000x.history": No such file or directory
  • From: Kyotaro Horiguchi
• Re:
  • From: Ian Lawrence Barwick
• Re: gawk extension linux missing stuff in package manager fedora 36
  • From: Daniel Verite
• gawk extension linux missing stuff in package manager fedora 36
  • From: Jim McNamara
• FATAL: could not receive timeline history file from the primary server: ERROR: could not open file "pg_wal/0000000x.history": No such file or directory
  • From: pgdba pgdba
• Fwd:
  • From: Jim McNamara
• [no subject]
  • From: Jim McNamara
• Re: SQL state: 42601. Execption handling.
  • From: Kyotaro Horiguchi
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Merlin Moncure
• Re: SQL state: 42601. Execption handling.
  • From: Tom Lane
• SQL state: 42601. Execption handling.
  • From: Ц
• SQL state: 42601. Execption handling.
  • From: Ц
• SV: GSSAPI authentication
  • From: Niels Jespersen
• Re: [EXT] Re: Accessing composite type elements
  • From: Garfield Lewis
• Re: GSSAPI authentication
  • From: Michael van der Kolff
• Re: GSSAPI authentication
  • From: Michael van der Kolff
• Re: GSSAPI authentication
  • From: Michael van der Kolff
• SV: GSSAPI authentication
  • From: Niels Jespersen
• Re: GSSAPI authentication
  • From: Michael van der Kolff
• Re: GSSAPI authentication
  • From: Michael van der Kolff
• GSSAPI authentication
  • From: Niels Jespersen
• Re: Why password authentication failed for user "postgres"?
  • From: David G. Johnston
• Re: Why password authentication failed for user "postgres"?
  • From: Frank Finner
• Logical replication of large objects
  • From: Andreas Joseph Krogh
• Re: Window function?
  • From: John W Higgins
• Re: Call pstrdup() of palloc.h will change source string, please help!
  • From: Tom Lane
• Re: unoptimized nested loops
  • From: Tim Kelly
• Call pstrdup() of palloc.h will change source string, please help!
  • From: mengfanjun
• Re: Window function?
  • From: David G. Johnston
• Re: Why password authentication failed for user "postgres"?
  • From: Jeff Janes
• Re: Window function?
  • From: Tom Lane
• Re: Window function?
  • From: Robert Stanford
• Re: Window function?
  • From: Thiemo Kellner
• Window function?
  • From: Robert Stanford
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Tom Lane
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Re: '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: David G. Johnston
• '{"x": 42, "y": null}'::jsonb != '{"x": 42}'::jsonb ... Really?
  • From: Bryn Llewellyn
• Re: Why password authentication failed for user "postgres"?
  • From: Reid Thompson
• Why password authentication failed for user "postgres"?
  • From: BeginnerC
• Re: Logically replicated table has no visible rows
  • From: Jeff Ross
• Re: Max sane value for join_collapse_limit?
  • From: Philip Semanchuk
• Re: GIN theory
  • From: jian he
• Re: unoptimized nested loops
  • From: Tim Kelly
• GIN theory
  • From: huangning290@xxxxxxxxx
• Max sane value for join_collapse_limit?
  • From: Andreas Joseph Krogh
• Re: [EXT] Re: Accessing composite type elements
  • From: Merlin Moncure
• Re: unoptimized nested loops
  • From: Jeff Janes
• Re: [EXT] Re: Accessing composite type elements
  • From: Garfield Lewis
• Re: Accessing composite type elements
  • From: Tom Lane
• Accessing composite type elements
  • From: Garfield Lewis
• Re: Extended multivariate statistics are ignored (potentially related to high null fraction, not sure)
  • From: Danny Shemesh
• Re: How to display complicated Chinese character: Biang.
  • From: Laurenz Albe
• How to display complicated Chinese character: Biang.
  • From: jian he
• Re: unoptimized nested loops
  • From: Tom Lane
• Re: unoptimized nested loops
  • From: Jeff Janes
• Re: unoptimized nested loops
  • From: David Rowley
• Re: Extended multivariate statistics are ignored (potentially related to high null fraction, not sure)
  • From: Bruce Momjian
• Extended multivariate statistics are ignored (potentially related to high null fraction, not sure)
  • From: Danny Shemesh
• Re: function currtid2() in SQL and ESQL/C to get the new CTID of a row
  • From: Tom Lane
• function currtid2() in SQL and ESQL/C to get the new CTID of a row
  • From: Matthias Apitz
• Re: Order of rows in statement triggers NEW/OLD tables
  • From: Thomas Munro
• unoptimized nested loops
  • From: Tim Kelly
• Re: Database trigger (one server to another)
  • From: Adrian Klaver
• Database trigger (one server to another)
  • From: Muhammad Bilal Jamil
• Re: existing row not found by SELECT ... WHERE CTID = ?
  • From: Matthias Apitz
• Logically replicated table has no visible rows
  • From: Jeff Ross
• Re: Build Postgres On AIX
  • From: Tom Lane
• Build Postgres On AIX
  • From: Mark Hill
• Re: The use of partial, expressional indices in pg < 14
  • From: Tom Lane
• pgAdmin 4 v 6.9
  • From: Eric Katchan
• The use of partial, expressional indices in pg < 14
  • From: Danny Shemesh
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Shaheed Haque
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Shaheed Haque
• Re: existing row not found by SELECT ... WHERE CTID = ?
  • From: Matthias Apitz
• Re: autovacuum on primary blocking queries on replica?
  • From: Jeff Janes
• Re: JSONB index not in use, but is TOAST the real cause of slow query?
  • From: Jeff Janes
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Shaheed Haque
• Appending data locally to a logical replication subscriber
  • From: andrew cooke
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Imre Samu
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Imre Samu
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Shaheed Haque
• Re: Is it possible to index "deep" into a JSONB column?
  • From: Bryn Llewellyn
• Re: psql 15beta1 does not print notices on the console until transaction completes
  • From: Rob Sargent
• Re: psql 15beta1 does not print notices on the console until transaction completes
  • From: Adrian Klaver