Postgresql General Discussion

• Thread Index

• Re: Cannot convert partitioned table to a view
  • From: Tom Lane
• Cannot convert partitioned table to a view
  • From: Kouber Saparev
• [Beginner Question]How to generate a call-graph for project?
  • From: Wen Yi
• Aw: Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Karsten Hilbert
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Gavan Schneider
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Bryn Llewellyn
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Bryn Llewellyn
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Bryn Llewellyn
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Christophe Pettus
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Adrian Klaver
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Tom Lane
• Re: ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: David G. Johnston
• ('dog$house' = quote_ident('dog$house')) is surprisingly FALSE
  • From: Bryn Llewellyn
• Re: Postgres calendar?
  • From: Josef Šimánek
• Re: Number of updated rows with LibPQ
  • From: Tom Lane
• Re: Replication between Master PostgreSQL database version 9.6.1 and Standby/Slave PostgreSQL database version 10.17.
  • From: Christophe Pettus
• Replication between Master PostgreSQL database version 9.6.1 and Standby/Slave PostgreSQL database version 10.17.
  • From: Kaushal Shriyan
• Re: Number of updated rows with LibPQ
  • From: Laurenz Albe
• Number of updated rows with LibPQ
  • From: Dominique Devienne
• Re: Postgres calendar?
  • From: Peter Eisentraut
• RE: Streaming wal from primiry terminating
  • From: Lahnov, Igor
• Re: Postgres calendar?
  • From: Julien Rouhaud
• Re: Postgres calendar?
  • From: Adam Brusselback
• Re: Postgres calendar?
  • From: Joshua Drake
• Re: fully qualified domain names and .pgpass
  • From: Ron
• Re: Postgres calendar?
  • From: Fabrízio de Royes Mello
• Postgres calendar?
  • From: Bruce Momjian
• Re: fully qualified domain names and .pgpass
  • From: Jeffrey Walton
• Re: fully qualified domain names and .pgpass
  • From: Adrian Klaver
• Re: fully qualified domain names and .pgpass
  • From: Alvaro Herrera
• fully qualified domain names and .pgpass
  • From: Ron
• PGSQL Phriday #001 - Two truths and a lie about PostgreSQL
  • From: Ryan Booz
• Re: Incorrect resource manager data checksum in record with zfs and compression
  • From: John Bolliger
• Re: Incorrect resource manager data checksum in record with zfs and compression
  • From: Michael Paquier
• Incorrect resource manager data checksum in record with zfs and compression
  • From: John Bolliger
• Please explain what's c99 brain dead?
  • From: jacktby jacktby
• Re: postgresql 15 for RHEL RPMs available?
  • From: Michael Nolan
• Re: postgresql 15 for RHEL RPMs available?
  • From: Daniel Gustafsson
• Re: postgresql 15 for RHEL RPMs available?
  • From: Tom Lane
• Re: postgresql 15 for RHEL RPMs available?
  • From: Michael Nolan
• Re: postgresql 15 for RHEL RPMs available?
  • From: Steve Baldwin
• postgresql 15 for RHEL RPMs available?
  • From: Michael Nolan
• what is brain-dead about C99 inline functions?
  • From: jacktby jacktby
• C99's brain-dead
  • From: jacktby jacktby
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Tom Lane
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Bryn Llewellyn
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Ron
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Ron
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Christoph Moench-Tegeder
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Tom Lane
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Bryn Llewellyn
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Ron
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Ron
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Tom Lane
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Peter J. Holzer
• Re: Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Julien Rouhaud
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Christoph Moench-Tegeder
• Re: Example code Re: Singleton SELECT inside cursor loop
  • From: Peter J. Holzer
• Names of run-time configuration parameters (was: Limiting the operations that client-side code can perform upon its database backend's artifacts)
  • From: Peter J. Holzer
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Peter J. Holzer
• Example code Re: Singleton SELECT inside cursor loop
  • From: Ron
• Singleton SELECT inside cursor loop
  • From: Ron
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Is there Postgres ODBC binary for OSX?
  • From: Igor Korot
• RE: Postgresql database and application server compatibility
  • From: Rickson Marshall
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Peter J. Holzer
• Re: Postgresql database and application server compatibility
  • From: Laurenz Albe
• Re: Postgresql database and application server compatibility
  • From: Ron
• Re: NULL values and Java JDBC
  • From: Matthias Apitz
• Re: NULL values and Java JDBC
  • From: Rob Sargent
• NULL values and Java JDBC
  • From: Matthias Apitz
• Re: Is there Postgres ODBC binary for OSX?
  • From: Daniel Gustafsson
• Is there Postgres ODBC binary for OSX?
  • From: Igor Korot
• Postgresql database and application server compatibility
  • From: Rickson Marshall
• Re: [BeginnerQuestion]Why I compile lex.yy.c failed?
  • From: Tom Lane
• [BeginnerQuestion]Why I compile lex.yy.c failed?
  • From: Wen Yi
• RE: Streaming wal from primiry terminating
  • From: Lahnov, Igor
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Streaming wal from primiry terminating
  • From: Michael Paquier
• RE: Streaming wal from primiry terminating
  • From: Lahnov, Igor
• Re: Streaming wal from primiry terminating
  • From: Kyotaro Horiguchi
• Re: table inheritance and privileges
  • From: Ted Toth
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Peter J. Holzer
• Re: table inheritance and privileges
  • From: Tom Lane
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Peter J. Holzer
• table inheritance and privileges
  • From: Ted Toth
• Streaming wal from primiry terminating
  • From: Lahnov, Igor
• Re: is there still a memory leak with hash joins in PG 12.11 ?
  • From: Alvaro Herrera
• is there still a memory leak with hash joins in PG 12.11 ?
  • From: Zwettler Markus (OIZ)
• Re: pgbackrest Help Required
  • From: Inzamam Shafiq
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Julien Rouhaud
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Tom Lane
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Julien Rouhaud
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Julien Rouhaud
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Peter J. Holzer
• Re: Order by in a sub query when aggregating the main query
  • From: Federico
• Re: Findout long unused tables in database
  • From: Andreas Fröde
• Re: Findout long unused tables in database
  • From: Laurenz Albe
• Re: pgbackrest Help Required
  • From: Stephen Frost
• Re: Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Julien Rouhaud
• Re: Findout long unused tables in database
  • From: Andreas Kretschmer
• Re: Findout long unused tables in database
  • From: Andreas Fröde
• Re: Findout long unused tables in database
  • From: Laurenz Albe
• Limiting the operations that client-side code can perform upon its database backend's artifacts
  • From: Bryn Llewellyn
• Findout long unused tables in database
  • From: Andreas Fröde
• Re: Support functions for range types
  • From: Laurenz Albe
• Re: Support functions for range types
  • From: Kim Johan Andersson
• Re: Support functions for range types
  • From: Tom Lane
• Support functions for range types
  • From: Kim Johan Andersson
• Re: Order by in a sub query when aggregating the main query
  • From: Federico
• Re: Order by in a sub query when aggregating the main query
  • From: Tom Lane
• Order by in a sub query when aggregating the main query
  • From: Federico
• Re: problem with on conflict / do update using psql 14.4
  • From: Adrian Klaver
• Re: problem with on conflict / do update using psql 14.4
  • From: David G. Johnston
• Re: problem with on conflict / do update using psql 14.4
  • From: Christophe Pettus
• Re: problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: problem with on conflict / do update using psql 14.4
  • From: Christophe Pettus
• Re: problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: problem with on conflict / do update using psql 14.4
  • From: Christophe Pettus
• Re: problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: problem with on conflict / do update using psql 14.4
  • From: Christophe Pettus
• Re: problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: problem with on conflict / do update using psql 14.4
  • From: David G. Johnston
• Re: problem with on conflict / do update using psql 14.4
  • From: Steve Baldwin
• problem with on conflict / do update using psql 14.4
  • From: Barry Kimelman
• Re: i added Arabic Dictionary but how I know i'm using it
  • From: Mohammed falih
• How to handle logical replication 12->14, when our max_replication_slots gets overrun by inactive sync workers
  • From: hubert depesz lubaczewski
• Re: pg_dump failed with error code 255, but I don't see why
  • From: Jerry Sievers
• Re: Database Horizon
  • From: Laurenz Albe
• Validate the internal consistency of pg_dump output?
  • From: Ron
• Re: pg_dump failed with error code 255, but I don't see why
  • From: Ron
• Re: pg_dump failed with error code 255, but I don't see why
  • From: Tom Lane
• pg_dump failed with error code 255, but I don't see why
  • From: Ron
• Database Horizon
  • From: Goti
• Re: PCI-DSS Requirements
  • From: Ron
• Patroni question
  • From: Zwettler Markus (OIZ)
• Re: [EXT] pg_stat_activity.backend_xmin
  • From: Laurenz Albe
• Re: ECCN for PostgreSQL
  • From: Junwang Zhao
• Re: ECCN for PostgreSQL
  • From: Laurenz Albe
• Re: PCI-DSS Requirements
  • From: Laurenz Albe
• ECCN for PostgreSQL
  • From: YangYuping(杨瑜萍)
• Re: PCI-DSS Requirements
  • From: Inzamam Shafiq
• pgbackrest Help Required
  • From: Inzamam Shafiq
• RE: [EXT] pg_stat_activity.backend_xmin
  • From: Dirschel, Steve
• Re: 10.22 Windows binaries download? (zip "invalid" on Enterprisedb)
  • From: JITEN KUMAR SHAH
• Re: tcp settings
  • From: Rob Sargent
• Re: [EXT] pg_stat_activity.backend_xmin
  • From: Rob Sargent
• RE: [EXT] Re: pg_stat_activity.backend_xmin
  • From: Dirschel, Steve
• RE: 10.22 Windows binaries download? (zip "invalid" on Enterprisedb)
  • From: Thomas, Richard
• Re: PostgreSQL Rule does not work with deferred constraint.
  • From: Tom Lane
• Re: pg_stat_activity.backend_xmin
  • From: Laurenz Albe
• pg_stat_activity.backend_xmin
  • From: Dirschel, Steve
• Re: 10.22 Windows binaries download? (zip "invalid" on Enterprisedb)
  • From: Erik Wienhold
• Re: 10.22 Windows binaries download? (zip "invalid" on Enterprisedb)
  • From: Hillary Masha
• 10.22 Windows binaries download? (zip "invalid" on Enterprisedb)
  • From: Thomas, Richard
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Mladen Gogala
• Re: PostgreSQL Rule does not work with deferred constraint.
  • From: Laurenz Albe
• PostgreSQL Rule does not work with deferred constraint.
  • From: Louis Tian
• Re: tcp settings
  • From: Tom Lane
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Rob Sargent
• Re: tcp settings
  • From: Rob Sargent
• Re: tcp settings
  • From: Tom Lane
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Theodore M Rolle, Jr.
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Mladen Gogala
• Experience with Dell SRM/SRDF?
  • From: Ron
• tcp settings
  • From: Rob Sargent
• Re: PCI-DSS Requirements
  • From: Ron
• Re: GIST combo index condition chosen for users queries is different from table owner's query
  • From: Dennis White
• PCI-DSS Requirements
  • From: Inzamam Shafiq
• Aw: Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Karsten Hilbert
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Bryn Llewellyn
• Re[4]: CVE-2022-2625
  • From: misha1966 misha1966
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Adrian Klaver
• Re: GIST combo index condition chosen for users queries is different from table owner's query
  • From: Tom Lane
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Bryn Llewellyn
• GIST combo index condition chosen for users queries is different from table owner's query
  • From: Dennis White
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: David G. Johnston
• Re: I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Tom Lane
• I slipped up so that no existing role allows connection. Is rescue possible?
  • From: Bryn Llewellyn
• Re: Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Tom Lane
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: David G. Johnston
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Bryn Llewellyn
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Bryn Llewellyn
• Re: Suggest using boolean index with (bflag is true) condition for the query with (bflag = true) clause
  • From: Tom Lane
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Adrian Klaver
• Re: Suggest using boolean index with (bflag is true) condition for the query with (bflag = true) clause
  • From: Laurenz Albe
• Re: What ist the standard setting of FETCH_COUNT?
  • From: Pavel Stehule
• What ist the standard setting of FETCH_COUNT?
  • From: Tiaswin
• Fwd: Postgresql/Postgis: Trigger for historization/versioning
  • From: celati Laurent
• Suggest using boolean index with (bflag is true) condition for the query with (bflag = true) clause
  • From: Евгений Плискин
• pg RLS suggestions needed
  • From: Laura Smith
• Re: Re[4]: CVE-2022-2625
  • From: Laurenz Albe
• Re[4]: CVE-2022-2625
  • From: misha1966 misha1966
• Re: Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Tom Lane
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: David G. Johnston
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Bryn Llewellyn
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: David G. Johnston
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Adrian Klaver
• Re: Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Adrian Klaver
• Where's the doc for "array()" — as in "select array(values (17), (42))"
  • From: Bryn Llewellyn
• Re: Mysterious performance degradation in exceptional cases
  • From: Adrian Klaver
• Re: Mysterious performance degradation in exceptional cases
  • From: Matthias Apitz
• Re: Mysterious performance degradation in exceptional cases
  • From: Adrian Klaver
• Re: Mysterious performance degradation in exceptional cases
  • From: Matthias Apitz
• Logical Replication - Give One Subscription Priority Over Other Subscriptions
  • From: Avi Weinberg
• Re: get user info on log
  • From: Adrian Klaver
• Re: get user info on log
  • From: Adrian Klaver
• Re: Query Performance
  • From: sivapostgres@xxxxxxxxx
• Re: Query Performance
  • From: Peter J. Holzer
• Re: Query Performance
  • From: Ron
• Re: Query Performance
  • From: sivapostgres@xxxxxxxxx
• Re: get user info on log
  • From: Ganesh Korde
• Re: Extension rpath issues on MacOS
  • From: Christophe Pettus
• Re: Extension rpath issues on MacOS
  • From: Tom Lane
• Extension rpath issues on MacOS
  • From: Christophe Pettus
• Re: New message in PostgreSQL log regarding socket for statistics collector
  • From: Hilbert, Karin
• Re: New message in PostgreSQL log regarding socket for statistics collector
  • From: Christoph Moench-Tegeder
• RE: Bind Parameter is Too Big
  • From: Kluzak, Matthew C.
• New message in PostgreSQL log regarding socket for statistics collector
  • From: Hilbert, Karin
• Re: get user info on log
  • From: Marcos Pegoraro
• Re: Re[2]: CVE-2022-2625
  • From: Tom Lane
• Re: Re[2]: CVE-2022-2625
  • From: Laurenz Albe
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Mladen Gogala
• Re: get user info on log
  • From: Adrian Klaver
• Re: Mysterious performance degradation in exceptional cases
  • From: Adrian Klaver
• Re: CVE-2022-2625
  • From: Ron
• Re: Re[2]: CVE-2022-2625
  • From: Tom Lane
• Re: CVE-2022-2625
  • From: Ron
• Re: Re[2]: CVE-2022-2625
  • From: Guillaume Lelarge
• Re[2]: CVE-2022-2625
  • From: misha1966 misha1966
• Re[2]: CVE-2022-2625
  • From: misha1966 misha1966
• Re: CVE-2022-2625
  • From: Ron
• Re: Resolving host to IP address
  • From: Sebastien Flaesch
• Re: Re[2]: CVE-2022-2625
  • From: Laurenz Albe
• Re: Mysterious performance degradation in exceptional cases
  • From: Matthias Apitz
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re[2]: CVE-2022-2625
  • From: misha1966 misha1966
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Mladen Gogala
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Mladen Gogala
• Re: massive update on gin index
  • From: Marcos Pegoraro
• Re: massive update on gin index
  • From: Tom Lane
• Re: massive update on gin index
  • From: Marcos Pegoraro
• Re: massive update on gin index
  • From: Rob Sargent
• Re: massive update on gin index
  • From: Guyren Howe
• massive update on gin index
  • From: Marcos Pegoraro
• Re: CVE-2022-2625
  • From: Laurenz Albe
• understand pg_ndistinct type && Why with(autovacuum_enabled=off) some query estimate 100, some is 200.
  • From: jian he
• Re: Mysterious performance degradation in exceptional cases
  • From: Tom Lane
• Re: Mysterious performance degradation in exceptional cases
  • From: Adrian Klaver
• CVE-2022-2625
  • From: misha1966 misha1966
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Karsten Hilbert
• Mysterious performance degradation in exceptional cases
  • From: Matthias Apitz
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Karsten Hilbert
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Guillaume Lelarge
• Re: Postgresql acid components
  • From: Rama Krishnan
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role? >> CASE CLOSED
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Christophe Pettus
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Jeremy Smith
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Guillaume Lelarge
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• get user info on log
  • From: Marcos Pegoraro
• Re: Postgresql acid components
  • From: Adrian Klaver
• How to Build NLS Files
  • From: Mark Hill
• Postgresql acid components
  • From: Rama Krishnan
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Christophe Pettus
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Christophe Pettus
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Aw: Re: toast useless
  • From: Karsten Hilbert
• Re: toast useless
  • From: Ron
• Re: toast useless
  • From: Simon Riggs
• Re: toast useless
  • From: Marcos Pegoraro
• Re: toast useless
  • From: Simon Riggs
• toast useless
  • From: Marcos Pegoraro
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Tom Lane
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Christophe Pettus
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: David G. Johnston
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Christophe Pettus
• Re: Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: David G. Johnston
• Is it possible to stop sessions killing eachother when they all authorize as the same role?
  • From: Bryn Llewellyn
• Re: how to check specific user_name have “SELECT ON ALL TABLES IN SCHEMA <tableschema>” privilege or not ?
  • From: Joe Conway
• Re: unable to install pldebugger
  • From: shashidhar Reddy
• Re: pgBackRest on MacOS
  • From: Stephen Frost
• Re: unable to install pldebugger
  • From: Julien Rouhaud
• Re: Missing query plan for auto_explain.
  • From: Julien Rouhaud
• Re: unable to install pldebugger
  • From: shashidhar Reddy
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Support for dates before 4713 BC
  • From: Tom Lane
• Re: Support for dates before 4713 BC
  • From: Simon Riggs
• Re: Resolving host to IP address
  • From: Francisco Olarte
• Re: Support for dates before 4713 BC
  • From: Tom Lane
• Re: Resolving host to IP address
  • From: Sebastien Flaesch
• Re: Support for dates before 4713 BC
  • From: Simon Riggs
• Re: Resolving host to IP address
  • From: Francisco Olarte
• Re: Resolving host to IP address
  • From: Francisco Olarte
• Re: Resolving host to IP address
  • From: Tom Lane
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Tom Lane
• Re: unable to install pldebugger
  • From: Julien Rouhaud
• Re: unable to install pldebugger
  • From: Pavel Stehule
• unable to install pldebugger
  • From: shashidhar Reddy
• Re: Support for dates before 4713 BC
  • From: Watzinger, Alexander
• Resolving host to IP address
  • From: Sebastien Flaesch
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Daniel Gustafsson
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Peter Eisentraut
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Daniel Gustafsson
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Tom Lane
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Daniel Gustafsson
• Re: [EXT] Re: log_min_messages = warning
  • From: Junwang Zhao
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Tom Lane
• Re: lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Jeffrey Walton
• lippq client library and openssl initialization: PQinitOpenSSL()
  • From: Sebastien Flaesch
• Re: [Beginner Question]Where can I get the source of hstore?
  • From: Adrian Klaver
• Re: [Beginner Question]Where can I get the source of hstore?
  • From: Wen Yi
• Re: [Beginner Question]Where can I get the source of hstore?
  • From: Tom Lane
• [Beginner Question]Where can I get the source of hstore?
  • From: Wen Yi
• Re: pgBackRest on MacOS
  • From: Ron
• pgBackRest on MacOS
  • From: Marc
• Re: Missing query plan for auto_explain.
  • From: Maxim Boguk
• Re: ERROR: cache lookup failed for user mapping 476444
  • From: Shanker Singh
• Re: ERROR: cache lookup failed for user mapping 476444
  • From: Tom Lane
• Re: ERROR: cache lookup failed for user mapping 476444
  • From: shanker singh
• Re: ***SPAM*** Re: WARNING: could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted
  • From: Mladen Gogala
• Re: ***SPAM*** Re: WARNING: could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted
  • From: Perry Smith
• Re: WARNING: could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted
  • From: Mladen Gogala
• Re: WARNING: could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted
  • From: Tom Lane
• WARNING: could not open statistics file "pg_stat_tmp/global.stat": Operation not permitted
  • From: Perry Smith
• Re: [BeginnerQuestion]Why these is 6 rows in my SELECT statement?
  • From: hubert depesz lubaczewski
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: [BeginnerQuestion]Why these is 6 rows in my SELECT statement?
  • From: Ian Lawrence Barwick
• [BeginnerQuestion]Why these is 6 rows in my SELECT statement?
  • From: BeginnerC
• Re: [EXT] Re: log_min_messages = warning
  • From: Tom Lane
• RE: [EXT] Re: log_min_messages = warning
  • From: Dirschel, Steve
• Re: Feature proposal: immutable/sealed partitions (and maybe tables, too)
  • From: David Rowley
• Re: Feature proposal: immutable/sealed partitions (and maybe tables, too)
  • From: Levi Aul
• Re: Feature proposal: immutable/sealed partitions (and maybe tables, too)
  • From: David Rowley
• Re: [EXT] Re: log_min_messages = warning
  • From: Tom Lane
• RE: [EXT] Re: log_min_messages = warning
  • From: Dirschel, Steve
• Re: Feature proposal: immutable/sealed partitions (and maybe tables, too)
  • From: Ron
• Re: [EXT] Re: log_min_messages = warning
  • From: Tom Lane
• RE: [EXT] Re: log_min_messages = warning
  • From: Dirschel, Steve
• Re: log_min_messages = warning
  • From: Adrian Klaver
• Feature proposal: immutable/sealed partitions (and maybe tables, too)
  • From: Levi Aul
• log_min_messages = warning
  • From: Dirschel, Steve
• Re: Determine if a user and database are available
  • From: Jeffrey Walton
• Re: Postgres SQL unable to handle Null values for Text datatype
  • From: Christophe Pettus
• Re: Postgres SQL unable to handle Null values for Text datatype
  • From: Mladen Gogala
• RE: Unable to start replica after failover
  • From: Lahnov, Igor
• Re: Unable to start replica after failover
  • From: Alexander Kukushkin
• Re: Postgres SQL unable to handle Null values for Text datatype
  • From: Lutz Horn
• Postgres SQL unable to handle Null values for Text datatype
  • From: Karthik K L V
• Re: Changing the admin/postgres user password
  • From: David G. Johnston
• Re: Changing the admin/postgres user password
  • From: Christophe Pettus
• Changing the admin/postgres user password
  • From: Jeffrey Walton
• Re: Missing query plan for auto_explain.
  • From: Maxim Boguk
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• RE: Unable to archive logs in standby server
  • From: Meera Nair
• Re: How to check if checkpoint is finished in sql script?
  • From: hubert depesz lubaczewski
• How to check if checkpoint is finished in sql script?
  • From: Yi Sun
• Re: Creating constraint dynamically
  • From: sivapostgres@xxxxxxxxx
• Re: Unable to archive logs in standby server
  • From: Kyotaro Horiguchi
• Re: [Beginner Querstion]Where can I find the news of database?
  • From: Mladen Gogala
• Re: [Beginner Querstion]Where can I find the news of database?
  • From: Lutz Horn
• [Beginner Querstion]Where can I find the news of database?
  • From: BeginnerC
• Re: Determine if a user and database are available
  • From: Tom Lane
• Re: Determine if a user and database are available
  • From: Adrian Klaver
• Re: Determine if a user and database are available
  • From: Ron
• Re: Determine if a user and database are available
  • From: Tom Lane
• Re: Determine if a user and database are available
  • From: David G. Johnston
• Re: Determine if a user and database are available
  • From: Christophe Pettus
• Determine if a user and database are available
  • From: Jeffrey Walton
• RE: Unable to archive logs in standby server
  • From: Meera Nair
• Re: How to make PostreSQL utilities honor home directories?
  • From: Jeffrey Walton
• Re: Unable to archive logs in standby server
  • From: Christophe Pettus
• RE: Unable to archive logs in standby server
  • From: Meera Nair
• Re: How to make PostreSQL utilities honor home directories?
  • From: Peter J. Holzer
• Re: How to make PostreSQL utilities honor home directories?
  • From: Peter J. Holzer
• Re: Missing query plan for auto_explain.
  • From: Peter J. Holzer
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Missing query plan for auto_explain.
  • From: Julien Rouhaud
• Re: How to make PostreSQL utilities honor home directories?
  • From: Adrian Klaver
• Re: How to make PostreSQL utilities honor home directories?
  • From: Ken Tanzer
• Re: How to make PostreSQL utilities honor home directories?
  • From: Jeffrey Walton
• Re: How to make PostreSQL utilities honor home directories?
  • From: Tom Lane
• Re: How to make PostreSQL utilities honor home directories?
  • From: Jeffrey Walton
• Re: How to make PostreSQL utilities honor home directories?
  • From: Peter J. Holzer
• Re: How to make PostreSQL utilities honor home directories?
  • From: Peter
• Re: How to make PostreSQL utilities honor home directories?
  • From: Adrian Klaver
• Re: How to make PostreSQL utilities honor home directories?
  • From: Tom Lane
• Re: How to make PostreSQL utilities honor home directories?
  • From: Adrian Klaver
• How to make PostreSQL utilities honor home directories?
  • From: Jeffrey Walton
• Re: Bind Parameter is Too Big
  • From: Tom Lane
• Re: Bind Parameter is Too Big
  • From: Adrian Klaver
• RE: Bind Parameter is Too Big
  • From: Kluzak, Matthew C.
• Re: Bind Parameter is Too Big
  • From: Tom Lane
• Re: Bind Parameter is Too Big
  • From: Adrian Klaver
• Bind Parameter is Too Big
  • From: Kluzak, Matthew C.
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Diffs in PG output vs WAL
  • From: Christophe Pettus
• Diffs in PG output vs WAL
  • From: V
• Re: View definition changes after reloading pg_dump export
  • From: Ron
• Re: View definition changes after reloading pg_dump export
  • From: Wesley Schwengle
• Re: View definition changes after reloading pg_dump export
  • From: Tom Lane
• Re: Vacuum Full is not returning space to OS
  • From: Ron
• Re: Vacuum Full is not returning space to OS
  • From: Daniel Gustafsson
• Re: Vacuum Full is not returning space to OS
  • From: Ron
• Vacuum Full is not returning space to OS
  • From: Sushant Postgres
• View definition changes after reloading pg_dump export
  • From: Wesley Schwengle
• Re: Feature request for count_estimate(samplesize) aggregate or SAMPLE keyword
  • From: Torge
• Re: Feature request for count_estimate(samplesize) aggregate or SAMPLE keyword
  • From: Tom Lane
• Feature request for count_estimate(samplesize) aggregate or SAMPLE keyword
  • From: Torge
• Re: CREATE SUBSCRIPTION not picking up .pgpass while psql does
  • From: Kristjan Mustkivi
• Re: CREATE SUBSCRIPTION not picking up .pgpass while psql does
  • From: hubert depesz lubaczewski
• Re: CREATE SUBSCRIPTION not picking up .pgpass while psql does
  • From: Kristjan Mustkivi
• Re: CREATE SUBSCRIPTION not picking up .pgpass while psql does
  • From: hubert depesz lubaczewski
• CREATE SUBSCRIPTION not picking up .pgpass while psql does
  • From: Kristjan Mustkivi
• Re: Missing query plan for auto_explain.
  • From: Tom Lane
• RE: Unable to archive logs in standby server
  • From: Meera Nair
• Re: Missing query plan for auto_explain.
  • From: Alvaro Herrera
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Missing query plan for auto_explain.
  • From: Julien Rouhaud
• Re: Missing query plan for auto_explain.
  • From: Alvaro Herrera
• Missing query plan for auto_explain.
  • From: Matheus Martin
• Re: Unable to start replica after failover
  • From: Alexander Kukushkin
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Hillary Masha
• questions about snapshot building logic
  • From: Вадим Самохин
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Two questions about "pg_constraint"
  • From: Tom Lane
• Re: Two questions about "pg_constraint"
  • From: Christophe Pettus
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Two questions about "pg_constraint"
  • From: Christophe Pettus
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Restriction on table partition expressions
  • From: Ron
• Re: How to select based on the condition of a column exists
  • From: David G. Johnston
• How to select based on the condition of a column exists
  • From: Shaozhong SHI
• RE: Unable to start replica after failover
  • From: Lahnov, Igor
• Re: Restriction on table partition expressions
  • From: James Vanns
• Re: In a partition why 1st time encounter NULL then call minvfunc
  • From: David G. Johnston
• Re: Two questions about "pg_constraint"
  • From: Christophe Pettus
• In a partition why 1st time encounter NULL then call minvfunc
  • From: jian he
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Information_schema.table_constraints
  • From: Ravi Krishna
• Re: Information_schema.table_constraints
  • From: Adrian Klaver
• Information_schema.table_constraints
  • From: Ravi Krishna
• Re: Restriction on table partition expressions
  • From: David Rowley
• Re: Restriction on table partition expressions
  • From: David Rowley
• Restriction on table partition expressions
  • From: James Vanns
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re:Re: pg_dump without setting search_path
  • From: gzh
• Re: Unable to start replica after failover
  • From: Alexander Kukushkin
• Re: pg_dump without setting search_path
  • From: Adrian Klaver
• Re: pg_dump without setting search_path
  • From: David G. Johnston
• Re:Re: pg_dump without setting search_path
  • From: gzh
• Re: pg_dump without setting search_path
  • From: Tom Lane
• pg_dump without setting search_path
  • From: gzh
• Greg Sabino Mullane ? Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Two questions about "pg_constraint"
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Thomas Kellerer
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Hillary Masha
• Re: Two questions about "pg_constraint"
  • From: Tom Lane
• Re: Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Two questions about "pg_constraint"
  • From: Adrian Klaver
• Re: Two questions about "pg_constraint"
  • From: Adrian Klaver
• Re: Two questions about "pg_constraint"
  • From: Adrian Klaver
• Two questions about "pg_constraint"
  • From: Bryn Llewellyn
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Hillary Masha
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Hillary Masha
• Re: recovery_command has precedence over phisical slots?
  • From: Giovanni Biscontini
• Re: Question regarding failover behavior
  • From: Koen De Groote
• Re: Setting up a server with previous day data
  • From: Ron
• RE: Unable to start replica after failover
  • From: Lahnov, Igor
• Re: recovery_command has precedence over phisical slots?
  • From: Laurenz Albe
• Re: Setting up a server with previous day data
  • From: Peter J. Holzer
• Re: Unable to start replica after failover
  • From: Alexander Kukushkin
• Re: recovery_command has precedence over phisical slots?
  • From: Kyotaro Horiguchi
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: David G. Johnston
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: David G. Johnston
• Re: Setting up a server with previous day data
  • From: Ron
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Question regarding failover behavior
  • From: Koen De Groote
• Re: Setting up a server with previous day data
  • From: Stephen Frost
• Re: Corrupted Postgresql Microsoft Binaries
  • From: Adrian Klaver
• Corrupted Postgresql Microsoft Binaries
  • From: Hillary Masha
• Re: Possible values of DATESTYLE / PGDATESTYLE
  • From: Tom Lane
• Re: Possible values of DATESTYLE / PGDATESTYLE
  • From: Christoph Moench-Tegeder
• Possible values of DATESTYLE / PGDATESTYLE
  • From: Sebastien Flaesch
• RE: Unable to start replica after failover
  • From: Lahnov, Igor
• Re: Support for dates before 4713 BC
  • From: Erik Wienhold
• Re: Db log error
  • From: Tom Lane
• Re: Support for dates before 4713 BC
  • From: Peter J. Holzer
• Db log error
  • From: eswar reddy
• Re: Support for dates before 4713 BC
  • From: Simon Riggs
• Re: Unable to start replica after failover
  • From: Kyotaro Horiguchi
• Re: Support for dates before 4713 BC
  • From: Tom Browder
• Re: Support for dates before 4713 BC
  • From: Alvaro Herrera
• Re: Creating constraint dynamically
  • From: jian he
• Re: Support for dates before 4713 BC
  • From: stefan eichert
• Re: Creating constraint dynamically
  • From: Francisco Olarte
• Re: Creating constraint dynamically
  • From: JITEN KUMAR SHAH
• Re: Creating constraint dynamically
  • From: Wim Bertels
• Re: Creating constraint dynamically
  • From: sivapostgres@xxxxxxxxx
• Re: Can I get the number of results plus the results with a single query?
  • From: Wim Bertels
• Re: Support for dates before 4713 BC
  • From: Tom Lane
• Re: Support for dates before 4713 BC
  • From: Peter J. Holzer
• Re: Support for dates before 4713 BC
  • From: Adrian Klaver
• Re: With Recursive / Recursive View question
  • From: Peter J. Holzer
• Support for dates before 4713 BC
  • From: Watzinger, Alexander
• Re: ***SPAM*** Re: With Recursive / Recursive View question
  • From: Perry Smith
• Re: ***SPAM*** Re: With Recursive / Recursive View question
  • From: Perry Smith
• Re: With Recursive / Recursive View question
  • From: Christophe Pettus
• With Recursive / Recursive View question
  • From: Perry Smith
• Re: Monitoring multixact members growth
  • From: Jeremy Schneider
• Re: Monitoring multixact members growth
  • From: Peter Geoghegan
• Re: High Availability PostgresDB on K8s
  • From: Jan Kohnert
• Re: recovery_command has precedence over phisical slots?
  • From: Laurenz Albe
• Re: High Availability PostgresDB on K8s
  • From: Sumit Sengupta
• High Availability PostgresDB on K8s
  • From: Marco Schmucki
• RE: Monitoring multixact members growth
  • From: Vido Vlahinic
• Monitoring multixact members growth
  • From: Vido Vlahinic
• recovery_command has precedence over phisical slots?
  • From: Giovanni Biscontini
• Re:Re:Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• Re:Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• Re: ERROR: catalog is missing 3 attribute(s) for relid 150243
  • From: Tom Lane
• Re: ERROR: catalog is missing 3 attribute(s) for relid 150243
  • From: milist ujang
• Re: ERROR: catalog is missing 3 attribute(s) for relid 150243
  • From: Julien Rouhaud
• Re: Unable to Create or Drop Index Concurrently
  • From: Abdul Qoyyuum
• Re: Is it possible to keep indexes on different disk location?
  • From: Ron
• Re: ERROR: catalog is missing 3 attribute(s) for relid 150243
  • From: milist ujang
• SIReadLock vs hot_standby_feedback
  • From: Christophe Pettus
• Re: Is it possible to keep indexes on different disk location?
  • From: W.P.
• Re: Fwd: Data caching
  • From: Adrian Klaver
• Fwd: Data caching
  • From: Anant ngo
• Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: Adrian Klaver
• Re: Is it possible to keep indexes on different disk location?
  • From: Laurenz Albe
• Re: [(catch-ext)] Re: [(catch-ext)] Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Ivan N. Ivanov
• Re: Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: Torsten Krah
• Re:Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• Re:Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• ERROR: catalog is missing 3 attribute(s) for relid 150243
  • From: milist ujang
• Re:Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• Re: [(catch-ext)] Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Vijaykumar Jain
• Re: Unable to Create or Drop Index Concurrently
  • From: hubert depesz lubaczewski
• Re: Is it possible to keep indexes on different disk location?
  • From: hubert depesz lubaczewski
• Re: [(catch-ext)] Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Ivan N. Ivanov
• Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Vijaykumar Jain
• Is it possible to keep indexes on different disk location?
  • From: W.P.
• Re: Unable to Create or Drop Index Concurrently
  • From: Christophe Pettus
• Unable to Create or Drop Index Concurrently
  • From: Abdul Qoyyuum
• Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Ron
• Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: Adrian Klaver
• Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: David Rowley
• Re: Different execution plan between PostgreSQL 8.2 and 12.5
  • From: Tom Lane
• Different execution plan between PostgreSQL 8.2 and 12.5
  • From: gzh
• Re: [(catch-ext)] Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Ivan N. Ivanov
• Re: Setting up streaming replication on large database (20+ TB) for the first time
  • From: Christophe Pettus
• Setting up streaming replication on large database (20+ TB) for the first time
  • From: Ivan N. Ivanov
• Re: i added Arabic Dictionary but how I know i'm using it
  • From: Laurenz Albe
• Re: Sub:column "" is of type bigint but expression is of type character varying
  • From: David G. Johnston
• Re: Sub:column "" is of type bigint but expression is of type character varying
  • From: Adrian Klaver
• Re: Postgres question
  • From: Thomas Kellerer
• Re: Postgres question
  • From: ajay venki
• Re: Sub:column "" is of type bigint but expression is of type character varying
  • From: JITEN KUMAR SHAH
• Re: Postgres question
  • From: hubert depesz lubaczewski
• Postgres question
  • From: ajay venki
• Sub:column "" is of type bigint but expression is of type character varying
  • From: Rama Krishnan
• Re: Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Ron
• i added Arabic Dictionary but how I know i'm using it
  • From: Mohammed falih
• Re: Can I get the number of results plus the results with a single query?
  • From: Peter J. Holzer
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Peter Eisentraut
• Re: Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Tatsuo Ishii
• RE: Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Aravind Phaneendra
• Re: Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Adrian Klaver
• Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Aravind Phaneendra
• Regarding availability of 32bit client drivers for postgresql 13/14
  • From: Aravind Phaneendra
• Re: plpython/python string formatting
  • From: Adrian Klaver
• Re: plpython/python string formatting
  • From: Adrian Klaver
• plpython/python string formatting
  • From: Ted Toth
• Re: plpython questions
  • From: David G. Johnston
• Re: plpython questions
  • From: Adrian Klaver
• Re: plpython questions
  • From: Bruce Momjian
• plpython questions
  • From: Ted Toth
• Re: Can I get the number of results plus the results with a single query?
  • From: Bryn Llewellyn
• Re: Can I get the number of results plus the results with a single query?
  • From: Peter J. Holzer
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Bzm@g
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: hubert depesz lubaczewski
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Tom Lane
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: hubert depesz lubaczewski
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: hubert depesz lubaczewski
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Julien Rouhaud
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Ron
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: hubert depesz lubaczewski
• Re: Would it be possible to add functions to tab-completion in psql?
  • From: Ron
• Would it be possible to add functions to tab-completion in psql?
  • From: hubert depesz lubaczewski
• Re: ***SPAM*** Re: Can I get the number of results plus the results with a single query?
  • From: David Rowley
• Re: ***SPAM*** Re: Can I get the number of results plus the results with a single query?
  • From: Walter Dörwald
• Re: Help regarding Multi Tenancy with PostgreSQL
  • From: Abdul Qoyyuum
• Re: ***SPAM*** Re: Can I get the number of results plus the results with a single query?
  • From: Rob Sargent
• Re: ***SPAM*** Re: Can I get the number of results plus the results with a single query?
  • From: Perry Smith
• Re: Can I get the number of results plus the results with a single query?
  • From: Bryn Llewellyn
• Re: Can I get the number of results plus the results with a single query?
  • From: Peter J. Holzer
• Re: lateral join with union all
  • From: David G. Johnston
• lateral join with union all
  • From: jian he
• Help regarding Multi Tenancy with PostgreSQL
  • From: Gaurav Daunde
• Re: Can I get the number of results plus the results with a single query?
  • From: David G. Johnston
• Can I get the number of results plus the results with a single query?
  • From: Perry Smith
• RE: Unable to start replica after failover
  • From: Lahnov, Igor
• Re: limits, indexes, views and query planner
  • From: David Rowley
• limits, indexes, views and query planner
  • From: Marc Mamin
• Re: ERROR: savepoint "jdbc_savepoint_532" does not exist
  • From: Rob Sargent
• ERROR: savepoint "jdbc_savepoint_532" does not exist
  • From: FOUTE K. Jaurès
• Re: Migrating PostgreSQL Stored Procedures to MSSQL 2019 for example
  • From: hector vass
• Re: Could not load server certificate file "server.crt": No such file or directory.
  • From: howardnews
• Is ODBC list dead?
  • From: Igor Korot
• Re: Could not load server certificate file "server.crt": No such file or directory.
  • From: Adrian Klaver
• Could not load server certificate file "server.crt": No such file or directory.
  • From: howardnews
• Scale 19x presentations
  • From: Lawrence Layhee
• RE: Migrating PostgreSQL Stored Procedures to MSSQL 2019 for example
  • From: Joel Rabinovitch
• Call for Volunteers - pgconf.nyc 2022
  • From: Andreas 'ads' Scherbaum
• Migrating PostgreSQL Stored Procedures to MSSQL 2019 for example
  • From: Scott Simpson
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: David G. Johnston
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Julien Rouhaud
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Strategy for preparing a query containg dynamic case / when
  • From: David G. Johnston
• Re: Strategy for preparing a query containg dynamic case / when
  • From: Theofilos Theofovos
• Re: Postgres NOT IN vs NOT EXISTS optimization
  • From: Bruce Momjian
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: David G. Johnston
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Is ODBC list still alive?
  • From: Igor Korot
• Re: Modelling a web CMS in Postgres ... a little advice needed
  • From: Rob Sargent
• Re: Fwd: Modelling a web CMS in Postgres ... a little advice needed
  • From: Tony Shelver
• Re: Oddity that I don't understand
  • From: Perry Smith
• Oddity that I don't understand
  • From: Perry Smith
• Re: Fwd: Modelling a web CMS in Postgres ... a little advice needed
  • From: Laura Smith
• Strategy for preparing a query containg dynamic case / when
  • From: Theofilos Theofovos
• Re: Fwd: Modelling a web CMS in Postgres ... a little advice needed
  • From: Laura Smith
• Fwd: Modelling a web CMS in Postgres ... a little advice needed
  • From: Tony Shelver
• Aw: Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Karsten Hilbert
• Modelling a web CMS in Postgres ... a little advice needed
  • From: Laura Smith
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: David G. Johnston
• Surprising results from current_role in a "security invoker" trigger function in a "cascade delete via FK" scenario
  • From: Bryn Llewellyn
• Re: Surprisingly forgiving behavior when a case expression is terminated with "end case"
  • From: Bryn Llewellyn
• Re: Why is DEFAULT much faster than UPDATE?
  • From: Adrian Klaver
• Why is DEFAULT much faster than UPDATE?
  • From: André Hänsel
• Re: Surprisingly forgiving behavior when a case expression is terminated with "end case"
  • From: Adrian Klaver
• Re: Surprisingly forgiving behavior when a case expression is terminated with "end case"
  • From: Tom Lane
• Surprisingly forgiving behavior when a case expression is terminated with "end case"
  • From: Bryn Llewellyn
• Re: index row size 2720 exceeds btree version 4
  • From: Peter J. Holzer
• Re: pkg: two postgresql clients
  • From: Peter
• Re: index row size 2720 exceeds btree version 4
  • From: Albrecht Dreß
• pkg: two postgresql clients
  • From: ml
• index row size 2720 exceeds btree version 4
  • From: Daulat
• Re: Creating A GIN index on JSONB column (large database)
  • From: Ron
• Re: Creating A GIN index on JSONB column (large database)
  • From: Ron
• Re: Creating A GIN index on JSONB column (large database)
  • From: Taylor Smith
• Re: Creating A GIN index on JSONB column (large database)
  • From: Rob Sargent
• Re: Creating A GIN index on JSONB column (large database)
  • From: Taylor Smith
• Re: Creating A GIN index on JSONB column (large database)
  • From: Rob Sargent
• Creating A GIN index on JSONB column (large database)
  • From: Taylor Smith
• Re: pg_restore remap schema
  • From: Fabrice Chapuis
• Re: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Saul Perdomo
• Re: pg_restore remap schema
  • From: Marcos Pegoraro
• Re: pg_restore remap schema
  • From: Tom Lane
• Re: pg_restore remap schema
  • From: Guillaume Lelarge
• pg_restore remap schema
  • From: Fabrice Chapuis
• RE: 20220722-pg_dump: error: invalid number of parents 0 for table
  • From: Techsupport
• Re: tablesample clause doesnt support to be applied to subquery.
  • From: rob stone
• tablesample clause doesnt support to be applied to subquery.
  • From: Wind
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: Expr. extended stats are skipped with equality operator
  • From: Tomas Vondra
• Re: Expr. extended stats are skipped with equality operator
  • From: Tom Lane
• Re: Expr. extended stats are skipped with equality operator
  • From: Tomas Vondra
• Re: Question about locking
  • From: Frank Millman
• Re: Question about locking
  • From: Ron
• Question about locking
  • From: Frank Millman
• Re: How to choose new master from slaves.?
  • From: Ron
• Re: How to choose new master from slaves.?
  • From: Peter J. Holzer
• Re: How to choose new master from slaves.?
  • From: Ron
• Re: How to choose new master from slaves.?
  • From: Peter J. Holzer
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Peter J. Holzer
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Expr. extended stats are skipped with equality operator
  • From: Danny Shemesh
• Re: sequence id overflow ERROR using timescaledb
  • From: Julien Rouhaud
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Jan Wieck
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Joe Conway
• sequence id overflow ERROR using timescaledb
  • From: abrahim abrahao
• follower never to become master
  • From: Marco Lechner
• Re: Index only scans for expressional indices when querying for the expression
  • From: Tom Lane
• Re: Index only scans for expressional indices when querying for the expression
  • From: Danny Shemesh
• Re: Allow user to connect to replicas only
  • From: hubert depesz lubaczewski
• Allow user to connect to replicas only
  • From: Wiwwo Staff
• Re: Index only scans for expressional indices when querying for the expression
  • From: Tom Lane
• Re: PostgreSQL 14.4 ERROR: out of memory issues
  • From: Aleš Zelený
• Re: Index only scans for expressional indices when querying for the expression
  • From: Danny Shemesh
• Re: Index only scans for expressional indices when querying for the expression
  • From: David G. Johnston
• Re: Behavior of identity columns
  • From: Francisco Olarte
• Re: How to choose new master from slaves.?
  • From: Ron
• Index only scans for expressional indices when querying for the expression
  • From: Danny Shemesh
• Re: Behavior of identity columns
  • From: sivapostgres@xxxxxxxxx
• Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
  • From: Mateusz Henicz
• Re: Unable to start replica after failover
  • From: Kyotaro Horiguchi
• Re: Is Client connections via ca.crt only possible?
  • From: Rejo Oommen
• Re: BUG #17567: Unable to Set Max_Connection in Postgresql which has replicas
  • From: Poornima Venkatesan
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Francisco Olarte
• How to choose new master from slaves.?
  • From: Sacheen Birhade
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Adrian Klaver
• Re: Is Client connections via ca.crt only possible?
  • From: Thomas Guyot
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Julien Rouhaud
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Ron
• Re: Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Adrian Klaver
• Purpose of DEFERRABLE _and_ INITIALLY DEFERRED foreign key constraint checking?
  • From: Ron
• 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: Is Client connections via ca.crt only possible?
  • From: Thomas Guyot
• Re: Upgrading from 12.3 to 12.11
  • From: zaphod61
• Re: Upgrading from 12.3 to 12.11
  • From: Adrian Klaver
• Re: Upgrading from 12.3 to 12.11
  • From: Adrian Klaver
• Re: Upgrading from 12.3 to 12.11
  • From: zaphod61
• Re: Upgrading from 12.3 to 12.11
  • From: Adrian Klaver
• Re: Upgrading from 12.3 to 12.11
  • From: Christophe Pettus
• Re: Upgrading from 12.3 to 12.11
  • From: David G. Johnston
• Upgrading from 12.3 to 12.11
  • From: zaphod61
• Re: "Missing" column in Postgres logical replication update message
  • From: Kevin Martin
• Re: ICU is not supported in this build. install from source code.
  • From: Daniel Verite
• Re: "Missing" column in Postgres logical replication update message
  • From: Tom Lane
• Why is my table continuousely written? -> XID issue?
  • From: Peter
• Re: "Missing" column in Postgres logical replication update message
  • From: Kevin Martin
• Re: "Missing" column in Postgres logical replication update message
  • From: Adrian Klaver
• Re: "Missing" column in Postgres logical replication update message
  • From: Adrian Klaver
• "Missing" column in Postgres logical replication update message
  • From: Kevin Martin
• Why is my table continuousely written?
  • From: Peter
• Re: ICU is not supported in this build. install from source code.
  • From: jian he
• Re: Strange collation names ("hu_HU.UTF-8")
  • From: Thomas Munro
• Re: Copying records from TABLE_A to TABLE_B (in the same database)
  • From: Peter J. Holzer
• 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: Ron
• 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