Postgresql General Discussion

• Thread Index

• Re: dblink: give search_path
  • From: Thiemo Kellner, NHC Barhufpflege
• Re: psql variable to plpgsql?
  • From: Thiemo Kellner, NHC Barhufpflege
• Re: Planning to change autovacuum_vacuum_scale_factor value to zero. Please suggest me if any negative impact.
  • From: Laurenz Albe
• Re: Suggest the best values for the postgres configuration parameters
  • From: Laurenz Albe
• Re: psql variable to plpgsql?
  • From: Pavel Stehule
• Re: Barman versus pgBackRest
  • From: Thomas Poty
• Re: dblink: give search_path
  • From: Rene Romero Benavides
• Re: ERROR: found multixact from before relminmxid
  • From: Andres Freund
• Re: ERROR: found multixact from before relminmxid
  • From: Pavan Deolasee
• psql variable to plpgsql?
  • From: Thiemo Kellner
• dblink: give search_path
  • From: Thiemo Kellner
• Re: difference between checkpoint_segments and wal_keep_segments in postgres configuration file
  • From: Michael Paquier
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: ERROR: found multixact from before relminmxid
  • From: Andres Freund
• Re: Using enum instead of join tables
  • From: PT
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: Postgresql Split Brain: Which one is latest
  • From: Jehan-Guillaume (ioguix) de Rorthais
• Re: best way to write large data-streams quickly?
  • From: Jerry Sievers
• Planning to change autovacuum_vacuum_scale_factor value to zero. Please suggest me if any negative impact.
  • From: Raghavendra Rao J S V
• difference between checkpoint_segments and wal_keep_segments in postgres configuration file
  • From: Raghavendra Rao J S V
• Suggest the best values for the postgres configuration parameters
  • From: Raghavendra Rao J S V
• Re: Postgresql Split Brain: Which one is latest
  • From: Adrian Klaver
• Re: Postgresql Split Brain: Which one is latest
  • From: Vikas Sharma
• Re: Postgresql Split Brain: Which one is latest
  • From: Adrian Klaver
• Re: Postgresql Split Brain: Which one is latest
  • From: Ron
• Re: Postgresql Split Brain: Which one is latest
  • From: Vikas Sharma
• Re: Postgresql Split Brain: Which one is latest
  • From: Adrian Klaver
• Re: Multiple records returned by a JOIN
  • From: Alexander Farber
• Re: Multiple records returned by a JOIN
  • From: Alexander Farber
• Re: Multiple records returned by a JOIN
  • From: David G. Johnston
• Multiple records returned by a JOIN
  • From: Alexander Farber
• Re: Postgresql Split Brain: Which one is latest
  • From: Edson Carlos Ericksson Richter
• Re: Postgresql Split Brain: Which one is latest
  • From: Melvin Davidson
• Re: Postgresql Split Brain: Which one is latest
  • From: Vikas Sharma
• Re: Postgresql Split Brain: Which one is latest
  • From: Adrian Klaver
• Re: Postgresql Split Brain: Which one is latest
  • From: Achilleas Mantzios
• Re: best way to write large data-streams quickly?
  • From: Mark Moellering
• Postgresql Split Brain: Which one is latest
  • From: Vikas Sharma
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Adam Sjøgren
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Pavan Deolasee
• Using enum instead of join tables
  • From: hmidi slim
• Grant to a group defined in Windows AD
  • From: Hans Schou
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: ERROR: found multixact from before relminmxid
  • From: Andres Freund
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: karthik kumar
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: Adrian Klaver
• Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: Adrian Klaver
• Re: Rationale for aversion to the central database?
  • From: Tim Cross
• Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: karthik kumar
• Re: ERROR: found multixact from before relminmxid
  • From: Peter Geoghegan
• Re: Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: Adrian Klaver
• Fwd: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: karthik kumar
• Re: Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: Adrian Klaver
• Carto ODBC_FDW issue "ERROR: Connecting to driver" from PG to DB2
  • From: karthik kumar
• Re: Conflict between JSON_AGG and COPY
  • From: Adrian Klaver
• Re: Conflict between JSON_AGG and COPY
  • From: Daniel Verite
• Re: algo for canceling a deadlocked transaction
  • From: Thomas Poty
• Re: How to monitor logical replication initial sync?
  • From: Peter Eisentraut
• Re: List all columns referencing an FK
  • From: Peter Eisentraut
• Re: best way to write large data-streams quickly?
  • From: Steve Atkins
• best way to write large data-streams quickly?
  • From: Mark Moellering
• Re: algo for canceling a deadlocked transaction
  • From: Tom Lane
• Re: algo for canceling a deadlocked transaction
  • From: Christophe Pettus
• Re: algo for canceling a deadlocked transaction
  • From: Thomas Poty
• Re: Conflict between JSON_AGG and COPY
  • From: David G. Johnston
• Re: Conflict between JSON_AGG and COPY
  • From: Adrian Klaver
• Re: Rationale for aversion to the central database?
  • From: Peter J. Holzer
• Re: ERROR: found multixact from before relminmxid
  • From: Tomas Vondra
• Re: Rationale for aversion to the central database?
  • From: Melvin Davidson
• Re: algo for canceling a deadlocked transaction
  • From: Stephen Frost
• algo for canceling a deadlocked transaction
  • From: Thomas Poty
• Re: Rationale for aversion to the central database?
  • From: Ray Cote
• Re: Rationale for aversion to the central database?
  • From: Peter J. Holzer
• Re: pg_stat_all_tables not updated when VACUUM ANALYZE execution finishes
  • From: Adrian Klaver
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• pg_stat_all_tables not updated when VACUUM ANALYZE execution finishes
  • From: Sebastien Arod
• Re: Conflict between JSON_AGG and COPY
  • From: Đỗ Ngọc Trí Cường
• Re: Rationale for aversion to the central database?
  • From: Peter Klipstein
• Re: Rationale for aversion to the central database?
  • From: Tim Cross
• Re: Rationale for aversion to the central database?
  • From: Stephen Frost
• Re: Rationale for aversion to the central database?
  • From: Stephen Frost
• Re: Rationale for aversion to the central database?
  • From: Ravi Krishna
• Re: Rationale for aversion to the central database?
  • From: g@xxxxxxxxxx
• Re: Rationale for aversion to the central database?
  • From: Adrian Klaver
• Re: Rationale for aversion to the central database?
  • From: Ravi Krishna
• Re: Rationale for aversion to the central database?
  • From: Alvaro Aguayo Garcia-Rada
• Rationale for aversion to the central database?
  • From: Guyren Howe
• Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Adrian Klaver
• Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Rory Campbell-Lange
• Re: Conflict between JSON_AGG and COPY
  • From: Adrian Klaver
• Re: Sum of written buffers bigger than allocation?
  • From: Jeff Janes
• Sum of written buffers bigger than allocation?
  • From: pinker
• Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Adrian Klaver
• Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Rory Campbell-Lange
• Conflict between JSON_AGG and COPY
  • From: Đỗ Ngọc Trí Cường
• Re: dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Adrian Klaver
• dump/restore problem due to CVE-2018-1058 (9.5.12)
  • From: Rory Campbell-Lange
• Re: dealing with lock
  • From: Thomas Poty
• Re: dealing with lock
  • From: Thomas Poty
• Re: dealing with lock
  • From: Thomas Kellerer
• Re: FDW with DB2
  • From: Ravi Krishna
• Re: FDW with DB2
  • From: Steven Hirsch
• Re: FDW with DB2
  • From: Ravi Krishna
• Re: dealing with lock
  • From: Adrian Klaver
• Re: FDW with DB2
  • From: Steven Hirsch
• Re: FDW with DB2
  • From: Ravi Krishna
• Re: FDW with DB2
  • From: Joshua D. Drake
• FDW with DB2
  • From: Ravi Krishna
• Re: dealing with lock
  • From: Thomas Poty
• Re: ERROR: found multixact from before relminmxid
  • From: Tomas Vondra
• Re: dealing with lock
  • From: Laurenz Albe
• dealing with lock
  • From: Thomas Poty
• Re: ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: decompose big queries
  • From: Steven Hirsch
• Re: decompose big queries
  • From: Melvin Davidson
• Re: decompose big queries
  • From: pinker
• Re: decompose big queries
  • From: Edson Carlos Ericksson Richter
• RE: LDAP Bind Password
  • From: Kumar, Virendra
• Re: ERROR: found multixact from before relminmxid
  • From: Tomas Vondra
• Re: Extract dates of a given day
  • From: rob stone
• Re: Extract dates of a given day
  • From: mariusz
• Extract dates of a given day
  • From: hmidi slim
• Re: pg_basebackup or dump for starting replication process
  • From: Laurenz Albe
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Pavan Deolasee
• ERROR: found multixact from before relminmxid
  • From: Alexandre Arruda
• Re: decompose big queries
  • From: David G. Johnston
• decompose big queries
  • From: hmidi slim
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Tom Lane
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Jerry Sievers
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Bruce Momjian
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Adam Sjøgren
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Jerry Sievers
• Re: Docker + postgreSQL : OOM killing in a large Group by operation
  • From: Tom Lane
• Docker + postgreSQL : OOM killing in a large Group by operation
  • From: Jorge Daniel
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Adam Sjøgren
• pg_basebackup or dump for starting replication process
  • From: PegoraroF10
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Tom Lane
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Adam Sjøgren
• Re: ERROR: unexpected chunk number 0 (expected 1) for toast value 76753264 in pg_toast_10920100
  • From: Adam Sjøgren
• Re: Concurrent CTE
  • From: Dorian Hoxha
• AW: Concurrent CTE
  • From: kpi6288
• Re: Concurrent CTE
  • From: Thomas Munro
• Re: Concurrent CTE
  • From: David G. Johnston
• Re: Concurrent CTE
  • From: Thomas Munro
• Re: Concurrent CTE
  • From: David G. Johnston
• Re: Concurrent CTE
  • From: Jeremy Finzel
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Jerry Sievers
• Re: Extension make installcheck: include update/insert feedback?
  • From: Tom Lane
• Re: LDAP Bind Password
  • From: Peter Eisentraut
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Bruce Momjian
• Extension make installcheck: include update/insert feedback?
  • From: Paul Jungwirth
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Jerry Sievers
• SQL statement in an error report for deferred constraint violation.
  • From: Konrad Witaszczyk
• Re: PgUpgrade bumped my XIDs by ~50M?
  • From: Bruce Momjian
• PgUpgrade bumped my XIDs by ~50M?
  • From: Jerry Sievers
• Re: Concatenate of values in hierarchical data
  • From: Alban Hertroys
• Concurrent CTE
  • From: Artur Formella
• Re: dblink: could not send query: another command is already in progress
  • From: Laurenz Albe
• Re: dblink: could not send query: another command is already in progress
  • From: Thiemo Kellner
• LDAP Bind Password
  • From: Kumar, Virendra
• Re: single sql, multiple schemas, one result set
  • From: Rob Sargent
• Re: single sql, multiple schemas, one result set
  • From: Guyren Howe
• single sql, multiple schemas, one result set
  • From: PegoraroF10
• Re: How to get an inclusive interval when using daterange
  • From: Paul Jungwirth
• Re: How to get an inclusive interval when using daterange
  • From: hmidi slim
• Re: is pg_advisory_lock() suitable for long runs
  • From: Merlin Moncure
• Re: Seems like there is an issue with reltuples showing twice the number of rows
  • From: Ranjith Ramachandra
• Re: How to get an inclusive interval when using daterange
  • From: Adrian Klaver
• Re: How to get an inclusive interval when using daterange
  • From: hmidi slim
• Re: Seems like there is an issue with reltuples showing twice the number of rows
  • From: Tom Lane
• Re: How to install pgTAP on cenos machine
  • From: Adrian Klaver
• Re: Seems like there is an issue with reltuples showing twice the number of rows
  • From: Tomas Vondra
• Re: Autovacuum Problem
  • From: Vitaliy Garnashevich
• How to install pgTAP on cenos machine
  • From: Raghavendra Rao J S V
• Re: dblink: could not send query: another command is already in progress
  • From: Laurenz Albe
• Seems like there is an issue with reltuples showing twice the number of rows
  • From: Ranjith Ramachandra
• Re: Autovacuum Problem
  • From: Achilleas Mantzios
• Re: Autovacuum Problem
  • From: Kein Name
• Re: Autovacuum Problem
  • From: Achilleas Mantzios
• Re: Autovacuum Problem
  • From: Kein Name
• Concatenate of values in hierarchical data
  • From: Mr. Baseball 34
• Re: Autovacuum Problem
  • From: Achilleas Mantzios
• Autovacuum Problem
  • From: Kein Name
• Re: PostgreSQL Cascade streaming replication problem
  • From: Jakub Janeček
• Re: PostgreSQL Cascade streaming replication problem
  • From: Jakub Janeček
• Re: PostgreSQL Cascade streaming replication problem
  • From: Michael Paquier
• Re: How to get an inclusive interval when using daterange
  • From: Tom Lane
• How to get an inclusive interval when using daterange
  • From: hmidi slim
• Re: Please suggest the best suited unit test frame work for postgresql database.
  • From: Rob Sargent
• Re: Please suggest the best suited unit test frame work for postgresql database.
  • From: Steven Lembark
• PostgreSQL Cascade streaming replication problem
  • From: Jakub Janeček
• Re: unreliable behaviour of track_functions
  • From: Adrian Klaver
• Re: Please suggest the best suited unit test frame work for postgresql database.
  • From: Adrian Klaver
• Re: unreliable behaviour of track_functions
  • From: pinker
• Re: unreliable behaviour of track_functions
  • From: pinker
• Re: unreliable behaviour of track_functions
  • From: pinker
• Please suggest the best suited unit test frame work for postgresql database.
  • From: Raghavendra Rao J S V
• Re: unreliable behaviour of track_functions
  • From: Adrian Klaver
• Re: unreliable behaviour of track_functions
  • From: pinker
• Re: unreliable behaviour of track_functions
  • From: Adrian Klaver
• unreliable behaviour of track_functions
  • From: pinker
• is pg_advisory_lock() suitable for long runs
  • From: Radoslav Nedyalkov
• Re: Problem with connection to host (wrong host)
  • From: Melvin Davidson
• Re: Problem with connection to host (wrong host)
  • From: Peter Eisentraut
• Problem with connection to host (wrong host)
  • From: Mike Martin
• Re: Redacting params in PostgreSQL logs
  • From: Vijaykumar Jain
• Re: Redacting params in PostgreSQL logs
  • From: Vijaykumar Jain
• Redacting params in PostgreSQL logs
  • From: Vijaykumar Jain
• Re: dblink: could not send query: another command is already in progress
  • From: Thiemo Kellner
• Schema-based replication
  • From: Moreno Andreo
• Re: Asynchronous Trigger?
  • From: Adam Tauno Williams
• Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring
  • From: Achilleas Mantzios
• Re: dblink: could not send query: another command is already in progress
  • From: Laurenz Albe
• Re: dblink: could not send query: another command is already in progress
  • From: Thiemo Kellner
• Re: Asynchronous Trigger?
  • From: Laurenz Albe
• Re: dblink: could not send query: another command is already in progress
  • From: Laurenz Albe
• Re: Autovacuum behavior with rapid insert/delete 9.6
  • From: Peter Geoghegan
• Autovacuum behavior with rapid insert/delete 9.6
  • From: Ted Filmore
• Asynchronous Trigger?
  • From: Cory Tucker
• dblink: could not send query: another command is already in progress
  • From: Thiemo Kellner
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: Cory Tucker
• Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring
  • From: Alvar Freude
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: Tom Lane
• Question about AWS Calculator
  • From: Ravi Krishna
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: Cory Tucker
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: David Rowley
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: Cory Tucker
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: Tom Lane
• Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring
  • From: Alvar C.H. Freude
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ben Madin
• Re: Question about buffers_alloc in pg_stat_bgwriter view for monitoring
  • From: Gunnar "Nick" Bluth
• Re: Bad Query Plans on 10.3 vs 9.6
  • From: David Rowley
• Re: Using Lateral
  • From: Johann Spies
• Bad Query Plans on 10.3 vs 9.6
  • From: Cory Tucker
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Adrian Klaver
• Re: Autonomous transaction, background worker
  • From: Thiemo Kellner
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: David G. Johnston
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Rob Sargent
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ken Beck
• Re: pg_ctl promote causes error "could not read block" (PG 9.5.0 and 9.5.4)
  • From: Michael Paquier
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Adrian Klaver
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ken Beck
• Re: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Tom Lane
• Re: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Cory Tucker
• Re: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Cory Tucker
• Re: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Tom Lane
• RE: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Kumar, Virendra
• RE: Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Kumar, Virendra
• Query Crashes PG 10.3 using partitions, works on 9.6
  • From: Cory Tucker
• Question about buffers_alloc in pg_stat_bgwriter view for monitoring
  • From: Alvar Freude
• Using Lateral
  • From: David G. Johnston
• Re: Using Lateral
  • From: Paul Jungwirth
• Re: [EXTERNAL]Re: pg_dump -Fd -j2 on standby in 9.6.6
  • From: David G. Johnston
• Re: [EXTERNAL]Re: pg_dump -Fd -j2 on standby in 9.6.6
  • From: Ron
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Moreno Andreo
• pg_ctl promote causes error "could not read block" (PG 9.5.0 and 9.5.4)
  • From: raj 1988
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Adrian Klaver
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Moreno Andreo
• Query performance with cluster
  • From: hmidi slim
• Re: Problem with postgreSQL
  • From: Adrian Klaver
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Tomas Vondra
• Re: Using Lateral
  • From: Johann Spies
• Re: Connection hangs on new created schema
  • From: Juan Manuel Cuello
• Re: Fixed chars
  • From: Enrico Pirozzi
• Re: Fixed chars
  • From: Andreas Kretschmer
• Fixed chars
  • From: Enrico Pirozzi
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: [EXTERNAL]Re: pg_dump -Fd -j2 on standby in 9.6.6
  • From: Andreas Kretschmer
• RE: [EXTERNAL]Re: pg_dump -Fd -j2 on standby in 9.6.6
  • From: Stefan Petrea
• Re: Connection hangs on new created schema
  • From: Laurenz Albe
• Re: Issue with PostgreSQL replication and PITR
  • From: Laurenz Albe
• Re: Hello all, I wanted to install any postgresql database for my development
  • From: Thomas Kellerer
• Hello all, I wanted to install any postgresql database for my development
  • From: sanjeev kumar
• Re: pg_dump -Fd -j2 on standby in 9.6.6
  • From: Andreas Kretschmer
• RE: [EXTERNAL]pg_dump -Fd -j2 on standby in 9.6.6
  • From: Stefan Petrea
• pg_dump -Fd -j2 on standby in 9.6.6
  • From: Stefan Petrea
• Re: connection dropped from the backend server
  • From: Adrian Klaver
• Re: connection dropped from the backend server
  • From: armand pirvu
• Re: connection dropped from the backend server
  • From: armand pirvu
• Re: connection dropped from the backend server
  • From: Tom Lane
• Re: connection dropped from the backend server
  • From: Adrian Klaver
• Re: connection dropped from the backend server
  • From: armand pirvu
• Re: connection dropped from the backend server
  • From: Adrian Klaver
• Re: Postgres Foreign Data Wrapper and DB2 LUW
  • From: legrand legrand
• Re: Troubleshooting a segfault and instance crash
  • From: Blair Boadway
• connection dropped from the backend server
  • From: armand pirvu
• Re: ERROR: invalid byte sequence for encoding "UTF8": 0xfc
  • From: armand pirvu
• Congrats to PostgreSQL sponsor OpenSCG
  • From: Joshua D. Drake
• Re: Postgres Foreign Data Wrapper and DB2 LUW
  • From: ajmcello
• Re: Proposition for better performance
  • From: armand pirvu
• Connection hangs on new created schema
  • From: Juan Manuel Cuello
• Re: Proposition for better performance
  • From: Paul Jungwirth
• Postgres Foreign Data Wrapper and DB2 LUW
  • From: Rakesh Kumar
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Adrian Klaver
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Tim Cross
• ERROR: invalid byte sequence for encoding "UTF8": 0xfc
  • From: armand pirvu
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ken Beck
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ken Beck
• Re: Check constraints.
  • From: Steve Rogerson
• Re: Problem with postgreSQL
  • From: Adrian Klaver
• Re: Proposition for better performance
  • From: hmidi slim
• Re: Proposition for better performance
  • From: Paul Jungwirth
• Re: Proposition for better performance
  • From: Paul Jungwirth
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Adrian Klaver
• Re: Proposition for better performance
  • From: hmidi slim
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Moreno Andreo
• Re: Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Joshua D. Drake
• Postgresql 9.3 Server will not start after Ubuntu Upgrade
  • From: Ken Beck
• Re: Proposition for better performance
  • From: Paul Jungwirth
• Re: Proposition for better performance
  • From: hmidi slim
• Re: Problem with postgreSQL
  • From: Adrian Klaver
• Re: Proposition for better performance
  • From: Paul Jungwirth
• Re: Using Lateral
  • From: Paul Jungwirth
• Re: Autonomous transaction, background worker
  • From: Paul Jungwirth
• Re: Check constraints.
  • From: Paul Jungwirth
• Proposition for better performance
  • From: hmidi slim
• logical decoder lsn order between transactions
  • From: Tom Dearman
• Re: Must re-connect to see tables
  • From: Daniel Verite
• Re: Must re-connect to see tables
  • From: Blake McBride
• Re: Must re-connect to see tables
  • From: rob stone
• Re: Must re-connect to see tables
  • From: Ron
• Check constraints.
  • From: Steve Rogerson
• Re: Must re-connect to see tables
  • From: Blake McBride
• Must re-connect to see tables
  • From: Blake McBride
• Using Lateral
  • From: Johann Spies
• Issue with PostgreSQL replication and PITR
  • From: Amee Sankhesara - Quipment India
• Re: Can't get policy to work correctly
  • From: Ivo Limmen
• Can't get policy to work correctly
  • From: Ivo Limmen
• Re: Warning of .partial wal file in PITR and Replication Environment
  • From: Michael Paquier
• Autonomous transaction, background worker
  • From: Thiemo Kellner
• Re: Problem with postgreSQL
  • From: Adrian Klaver
• Warning of .partial wal file in PITR and Replication Environment
  • From: Amee Sankhesara - Quipment India
• Problem with postgreSQL
  • From: Gian mario Caggiu
• Re: missing public on schema public
  • From: Michael Paquier
• Re: PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: Michael Paquier
• Re: PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: David G. Johnston
• Re: PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: nmmulla
• Re: PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: Joshua D. Drake
• Query performance
  • From: hmidi slim
• Re: missing public on schema public
  • From: Alvaro Herrera
• Re: PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: nmmulla
• PostgreSQL version on VMware vSphere ESXI 6.5 and harware version 13
  • From: nmmulla
• RE: Foreign Key locking / deadlock issue.... v2
  • From: HORDER Phil
• Re: pg_stat_statements: password in command is not obfuscated
  • From: Michael Paquier
• Re: Troubleshooting a segfault and instance crash
  • From: Pavel Stehule
• RE: Troubleshooting a segfault and instance crash
  • From: Jan Bilek
• Re: Troubleshooting a segfault and instance crash
  • From: Blair Boadway
• Re: Troubleshooting a segfault and instance crash
  • From: Peter Geoghegan
• Re: Troubleshooting a segfault and instance crash
  • From: Blair Boadway
• Re: Foreign Key locking / deadlock issue.... v2
  • From: Adrian Klaver
• RE: Foreign Key locking / deadlock issue.... v2
  • From: HORDER Phil
• Re: case and accent insensitive
  • From: Andreas Kretschmer
• Re: Foreign Key locking / deadlock issue.... v2
  • From: rob stone
• Re: primary key and unique index
  • From: Thomas Poty
• RE: primary key and unique index
  • From: HORDER Phil
• case and accent insensitive
  • From: MOISES ESPINOSA
• Re: pg_stat_statements: password in command is not obfuscated
  • From: David Rowley
• Re: FDW Foreign Table Access: strange LOG message
  • From: Tom Lane
• pg_stat_statements: password in command is not obfuscated
  • From: legrand legrand
• Re: FDW Foreign Table Access: strange LOG message
  • From: Albrecht Dreß
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Christoph Berg
• Re: JDBC connectivity issue
  • From: Dave Cramer
• RE: Foreign Key locking / deadlock issue.... v2
  • From: HORDER Phil
• Re: JDBC connectivity issue
  • From: JCMS22
• Re: JDBC connectivity issue
  • From: JCMS22
• RE: Use pgloader with FDW
  • From: Patricia DECHANDOL
• Re: Use pgloader with FDW
  • From: Alban Hertroys
• RE: Use pgloader with FDW
  • From: Patricia DECHANDOL
• Re: Use pgloader with FDW
  • From: Adrian Klaver
• RE: Use pgloader with FDW
  • From: Patricia DECHANDOL
• Re: Use pgloader with FDW
  • From: Adrian Klaver
• Re: Foreign Key locking / deadlock issue.... v2
  • From: rob stone
• Use pgloader with FDW
  • From: Patricia DECHANDOL
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: primary key and unique index
  • From: Achilleas Mantzios
• Re: primary key and unique index
  • From: David Rowley
• primary key and unique index
  • From: Thomas Poty
• Re: FDW Foreign Table Access: strange LOG message
  • From: Michael Paquier
• Re: FDW Foreign Table Access: strange LOG message
  • From: Tom Lane
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Peter Geoghegan
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: FDW Foreign Table Access: strange LOG message
  • From: Tom Lane
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Tomas Vondra
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Peter Geoghegan
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Alvaro Herrera
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: FDW Foreign Table Access: strange LOG message
  • From: Adrian Klaver
• Re: FDW Foreign Table Access: strange LOG message
  • From: Albrecht Dreß
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Tomas Vondra
• Re: Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases
  • From: Melvin Davidson
• Re: Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases
  • From: Tim Clarke
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases
  • From: Raymond O'Donnell
• Re: Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases
  • From: Steven Hirsch
• RE: Foreign Key locking / deadlock issue.... v2
  • From: HORDER Phil
• Re: Foreign Key locking / deadlock issue.... v2
  • From: rob stone
• Re: Prepared statements
  • From: Rakesh Kumar
• Introducing brand-new dbForge Studio for PostgreSQL, a powerful IDE for working with PostgreSQL databases
  • From: Devart
• Re: JDBC connectivity issue
  • From: Dave Cramer
• Re: Prepared statements
  • From: Laurenz Albe
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Tomas Vondra
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Rob Sargent
• Re: Prepared statements
  • From: Steve Atkins
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Peter Geoghegan
• Re: Prepared statements
  • From: Rakesh Kumar
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• Prepared statements
  • From: Tim Cross
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: JDBC connectivity issue
  • From: chris
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Rob Sargent
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Re: JDBC connectivity issue
  • From: chris
• Re: Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Tomas Vondra
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Louis Battuello
• Postgresql 10.3 , query never completes if LIMIT clause is specified and paralle processing is on
  • From: Alessandro Aste
• Foreign Key Validation after Reference Table Ownership Change
  • From: David G. Johnston
• Re: FDW Foreign Table Access: strange LOG message
  • From: Adrian Klaver
• Re: FDW Foreign Table Access: strange LOG message
  • From: Albrecht Dreß
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Tom Lane
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Adrian Klaver
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Louis Battuello
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Tom Lane
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Louis Battuello
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Vincenzo Romano
• Re: Re: Foreign Key Validation after Reference Table Ownership Change
  • From: David G. Johnston
• RE: Re: Foreign Key Validation after Reference Table Ownership Change
  • From: Battuello, Louis
• RE: Foreign Key locking / deadlock issue.... v2
  • From: HORDER Phil
• Re: Foreign Key Validation after Reference Table Ownership Change
  • From: David G. Johnston
• Foreign Key Validation after Reference Table Ownership Change
  • From: Battuello, Louis
• Re: Restore - disable triggers - when they fired?
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: Is there a way to get the name of the calling function in pgplsql?
  • From: Pavel Stehule
• RE: Foreign Key locking / deadlock issue.
  • From: HORDER Phil
• Re: Is there a way to get the name of the calling function in pgplsql?
  • From: Thiemo Kellner, NHC Barhufpflege
• Re: Foreign Key locking / deadlock issue.
  • From: rob stone
• Re: Restore - disable triggers - when they fired?
  • From: Durumdara
• Re: Is there a way to get the name of the calling function in pgplsql?
  • From: Pavel Stehule
• Is there a way to get the name of the calling function in pgplsql?
  • From: Thiemo Kellner
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Christoph Berg
• Re: FDW Foreign Table Access: strange LOG message
  • From: Tom Lane
• Re: FATAL: semctl(15073290, 4, SETVAL, 0) failed: Invalid argument
  • From: Adrian Klaver
• Re: You might be able to move the set-returning function into a LATERAL FROM item.
  • From: Alexander Farber
• Re: FDW Foreign Table Access: strange LOG message
  • From: Adrian Klaver
• FATAL: semctl(15073290, 4, SETVAL, 0) failed: Invalid argument
  • From: JotaComm
• FDW Foreign Table Access: strange LOG message
  • From: Albrecht Dreß
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: postgresql-10.3 on unbuntu-17.10 - how??
  • From: Adrian Klaver
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Enrico Thierbach
• Re: Restore - disable triggers - when they fired?
  • From: Adrian Klaver
• postgresql-10.3 on unbuntu-17.10 - how??
  • From: Stuart McGraw
• Re: Restore - disable triggers - when they fired?
  • From: Durumdara
• Re: Restore - disable triggers - when they fired?
  • From: Adrian Klaver
• Restore - disable triggers - when they fired?
  • From: Durumdara
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: You might be able to move the set-returning function into a LATERAL FROM item.
  • From: Tom Lane
• Re: Foreign Key locking / deadlock issue.
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: error 53200 out of memory
  • From: Adrian Klaver
• Re: Foreign Key locking / deadlock issue.
  • From: Adrian Klaver
• Re: COPY error when \. char
  • From: Adrian Klaver
• Foreign Key locking / deadlock issue.
  • From: HORDER Phil
• COPY error when \. char
  • From: Nicolas Paris
• Re: You might be able to move the set-returning function into a LATERAL FROM item.
  • From: Laurenz Albe
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• You might be able to move the set-returning function into a LATERAL FROM item.
  • From: Alexander Farber
• RE: error 53200 out of memory
  • From: francis cherat
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Peter Geoghegan
• Re: STRING_AGG and GROUP BY
  • From: David G. Johnston
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: STRING_AGG and GROUP BY
  • From: Alexander Farber
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Peter Geoghegan
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Andres Freund
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Andres Freund
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Andres Freund
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Andres Freund
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Alvaro Herrera
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Andreas Kretschmer
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Melvin Davidson
• Re: PostgreSQL 9.6 Temporary files
  • From: Melvin Davidson
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• found xmin from before relfrozenxid on pg_catalog.pg_authid
  • From: Jeremy Finzel
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Melvin Davidson
• Re: PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: PostgreSQL 9.6 Temporary files
  • From: Adrian Klaver
• Re: PostgreSQL 9.6 Temporary files
  • From: Andreas Kretschmer
• PostgreSQL 9.6 Temporary files
  • From: Jimmy Augustine
• Re: Logical replication: duplicate key problem
  • From: Adrian Klaver
• Logical replication: duplicate key problem
  • From: Johann Spies
• Re: pentaho timestamp issue
  • From: Tom Lane
• pentaho timestamp issue
  • From: PropAAS DBA
• Re: changing my mail address
  • From: Michael Paquier
• Re: changing my mail address
  • From: Stephen Frost
• Re: changing my mail address
  • From: Adrian Klaver
• Re: changing my mail address
  • From: Ron Johnson
• Re: changing my mail address
  • From: Stephen Frost
• Re: changing my mail address
  • From: Michelle Konzack
• Re: changing my mail address
  • From: Ron Johnson
• Re: What is the meaning of pg_restore output?
  • From: Adrian Klaver
• Re: changing my mail address
  • From: wambacher
• Re: changing my mail address
  • From: Stephen Frost
• changing my mail address
  • From: wambacher
• Re: What is the meaning of pg_restore output?
  • From: Alexandru Lazarev
• Re: Could not open extension control file “/usr/share/postgresql/10/extension/pg_similarity.control”: No such file or directory
  • From: Adrian Klaver
• Re: Could not open extension control file “/usr/share/postgresql/10/extension/pg_similarity.control”: No such file or directory
  • From: hmidi slim
• RE: error 53200 out of memory
  • From: francis cherat
• Re: Could not open extension control file “/usr/share/postgresql/10/extension/pg_similarity.control”: No such file or directory
  • From: Adrian Klaver
• Could not open extension control file “/usr/share/postgresql/10/extension/pg_similarity.control”: No such file or directory
  • From: hmidi slim
• Re: Want to disable fully qualified table names on pg_dump in pg_dump (PostgreSQL) 9.6.8
  • From: Adrian Klaver
• Re: Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Victoria Stuart (VictoriasJourney.com)
• Re: Want to disable fully qualified table names on pg_dump in pg_dump (PostgreSQL) 9.6.8
  • From: Foolish Ewe
• Re: Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Adrian Klaver
• Re: Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Victoria
• Re: ora2pg and invalid command \N
  • From: Julien Rouhaud
• Re: ora2pg and invalid command \N
  • From: Adrian Klaver
• Re: ora2pg and invalid command \N
  • From: Charlin Barak
• Re: Question on corruption (PostgreSQL 9.6.1)
  • From: Peter Geoghegan
• Re: ora2pg and invalid command \N
  • From: Pavel Stehule
• Re: Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Victoria
• Re: ora2pg and invalid command \N
  • From: Adrian Klaver
• ora2pg and invalid command \N
  • From: Charlin Barak
• Re: Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Adrian Klaver
• Nvim as external editor in psql as Postgres root user - .vimrc (environment?) issue
  • From: Victoria
• Re: STRING_AGG and GROUP BY
  • From: David G. Johnston
• Re: STRING_AGG and GROUP BY
  • From: Alexander Farber
• Re: STRING_AGG and GROUP BY
  • From: David G. Johnston
• Re: error 53200 out of memory
  • From: Adrian Klaver
• Re: Prompt for parameter value in psql
  • From: Pavel Stehule
• Re: Prompt for parameter value in psql
  • From: Melvin Davidson
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: David G. Johnston
• Prompt for parameter value in psql
  • From: Tiffany Thang
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Enrico Thierbach
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Enrico Thierbach
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• STRING_AGG and GROUP BY
  • From: Alexander Farber
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Melvin Davidson
• error 53200 out of memory
  • From: francis cherat
• Re: Question on corruption (PostgreSQL 9.6.1)
  • From: Andy Halsall
• RE: Circle and box intersect
  • From: Martin Moore
• Re: Circle and box intersect
  • From: Andreas Kretschmer
• Circle and box intersect
  • From: Martin Moore
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Tom Lane
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• Re: PgBackrest questions
  • From: Stephen Frost
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Melvin Davidson
• Re: PgBackrest questions
  • From: Stephen Frost
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• Re: PgBackrest questions
  • From: chiru r
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Melvin Davidson
• Re: Want to disable fully qualified table names on pg_dump in pg_dump (PostgreSQL) 9.6.8
  • From: Adrian Klaver
• Want to disable fully qualified table names on pg_dump in pg_dump (PostgreSQL) 9.6.8
  • From: Foolish Ewe
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Enrico Thierbach
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Melvin Davidson
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: Stephen Frost
• Re: psql output result
  • From: Tiffany Thang
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: David G. Johnston
• Re: SELECT .. FOR UPDATE: find out who locked a row
  • From: pinker
• SELECT .. FOR UPDATE: find out who locked a row
  • From: Enrico Thierbach
• ERROR: right sibling's left-link doesn't match: block 5 links to 8 instead of expected 2 in index "pg_toast_2619_index"
  • From: Raghavendra Rao J S V
• Re: wiki Disk Usage, table size: ERROR: could not open relation with OID 0
  • From: Hans Schou
• Re: wiki Disk Usage, table size: ERROR: could not open relation with OID 0
  • From: Hans Schou
• Re: psql output result
  • From: Adrian Klaver
• Re: psql output result
  • From: Geoff Winkless
• psql output result
  • From: Tiffany Thang
• Change ON UPDATE behavior of fkey
  • From: Mike Rylander
• Re: How to monitor logical replication initial sync?
  • From: bricklen
• Re: Snapshot recovery or rolling back commited
  • From: rob stone
• Snapshot recovery or rolling back commited
  • From: Marc-Antoine Nüssli
• Re: PgBackrest questions
  • From: chiru r
• Re: wiki Disk Usage, table size: ERROR: could not open relation with OID 0
  • From: Tom Lane
• Re: wiki Disk Usage, table size: ERROR: could not open relation with OID 0
  • From: Michael Paquier
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Alexander Farber
• Re: PgBackrest questions
  • From: Stephen Frost
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• PgBackrest questions
  • From: chiru r
• Re: JDBC connectivity issue
  • From: chris
• Re: Need followup setup instructions to postgresql-10.3-1-linux-x64.run
  • From: pinker
• Re: Best options for new PG instance
  • From: pinker
• Re: Primary key gist index?
  • From: Jeremy Finzel
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Ivan E. Panchenko
• Re: Primary key gist index?
  • From: Paul Jungwirth
• Re: Primary key gist index?
  • From: Steven Lembark
• Re: Primary key gist index?
  • From: Adrian Klaver
• Re: Primary key gist index?
  • From: Tom Lane
• Re: Primary key gist index?
  • From: Paul Jungwirth
• Re: Primary key gist index?
  • From: Jeremy Finzel
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Adrian Klaver
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Adrian Klaver
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Alexander Farber
• Re: Extract elements from JSON array and return them as concatenated string
  • From: Ivan E. Panchenko
• Extract elements from JSON array and return them as concatenated string
  • From: Alexander Farber
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• wiki Disk Usage, table size: ERROR: could not open relation with OID 0
  • From: Hans Schou
• Re: JDBC connectivity issue
  • From: chris
• Re: Primary key gist index?
  • From: Adrian Klaver
• Primary key gist index?
  • From: Jeremy Finzel
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• Re: Reindex doesn't eliminate bloat
  • From: Ron Johnson
• Re: JDBC connectivity issue
  • From: chris
• Re: Reindex doesn't eliminate bloat
  • From: Joe Conway
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Melvin Davidson
• Re: query_to_xml() returns invalid XML when query returns no rows
  • From: Peter Eisentraut
• Re: Is there a way to create a functional index that tables tableoid column as an arg?
  • From: Tom Lane
• Re: Is there a way to create a functional index that tables tableoid column as an arg?
  • From: Ryan Murphy
• Re: query_to_xml() returns invalid XML when query returns no rows
  • From: Thomas Kellerer
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Melvin Davidson
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Aldrin Martoq Ahumada
• Re: Programmatically duplicating a schema
  • From: Adrian Klaver
• Re: UPSERT on a view
  • From: Tom Lane
• Re: UPSERT on a view
  • From: Tom Lane
• Re: UPSERT on a view
  • From: Melvin Davidson
• Re: UPSERT on a view
  • From: David G. Johnston
• Re: Question on corruption (PostgreSQL 9.6.1)
  • From: Tom Lane
• Re: Programmatically duplicating a schema
  • From: David G. Johnston
• Re: UPSERT on a view
  • From: Melvin Davidson
• Question on corruption (PostgreSQL 9.6.1)
  • From: Andy Halsall
• UPSERT on a view
  • From: Steven Roth
• Re: Programmatically duplicating a schema
  • From: Melvin Davidson
• Re: Point-in-time recovery after failover
  • From: Laurenz Albe
• Point-in-time recovery after failover
  • From: Dylan Luong
• Re: Programmatically duplicating a schema
  • From: Alban Hertroys
• Re: Logical decoding on standby
  • From: Andreas Kretschmer
• Re: Programmatically duplicating a schema
  • From: matt . figg
• Re: Programmatically duplicating a schema
  • From: Adrian Klaver
• Re: Reindex doesn't eliminate bloat
  • From: Ron Johnson
• Re: Reindex doesn't eliminate bloat
  • From: Nikolay Samokhvalov
• Programmatically duplicating a schema
  • From: matt . figg
• Re: Logical decoding on standby
  • From: Andres Freund
• Sv: Re: Logical decoding on standby
  • From: Andreas Joseph Krogh
• Re: Logical decoding on standby
  • From: David G. Johnston
• Re: Logical decoding on standby
  • From: Andreas Kretschmer
• Re: Logical decoding on standby
  • From: Andreas Kretschmer
• Re: Reindex doesn't eliminate bloat
  • From: Ron Johnson
• Re: Reindex doesn't eliminate bloat
  • From: Adrian Klaver
• Re: query_to_xml() returns invalid XML when query returns no rows
  • From: Peter Eisentraut
• Re: Reindex doesn't eliminate bloat
  • From: Ron Johnson
• Re: Reindex doesn't eliminate bloat
  • From: Nikolay Samokhvalov
• Reindex doesn't eliminate bloat
  • From: Ron Johnson
• Logical decoding on standby
  • From: Andreas Joseph Krogh
• pglogical lag due to replication timeout
  • From: greigwise
• Re: psql in a bash function
  • From: Ron Johnson
• Re: psql in a bash function
  • From: Eric Raskin
• Re: psql in a bash function
  • From: Melvin Davidson
• psql in a bash function
  • From: Ron Johnson
• Re: can someone send a design document of "parallel work" to me?
  • From: Adrian Klaver
• can someone send a design document of "parallel work" to me?
  • From: lin
• query_to_xml() returns invalid XML when query returns no rows
  • From: Thomas Kellerer
• Re: Is there a way to create a functional index that tables tableoid column as an arg?
  • From: David Rowley
• Is there a way to create a functional index that tables tableoid column as an arg?
  • From: Ryan Murphy
• Re: wrong message when trying to create an already existing index
  • From: legrand legrand
• Re: momjian.us is down?
  • From: Bruce Momjian
• Re: Application Dependency/Limitations of Postgres Version Upgrade
  • From: Félix GERZAGUET
• Re: Application Dependency/Limitations of Postgres Version Upgrade
  • From: Adrian Klaver
• Re: wrong message when trying to create an already existing index
  • From: Tom Lane
• Re: wrong message when trying to create an already existing index
  • From: Adrian Klaver
• Re: wrong message when trying to create an already existing index
  • From: legrand legrand
• wrong message when trying to create an already existing index
  • From: legrand legrand
• Re: wrong message when trying to create an already existing index
  • From: legrand legrand
• Re: wrong message when trying to create an already existing index
  • From: Melvin Davidson
• RE: Application Dependency/Limitations of Postgres Version Upgrade
  • From: Alvaro Aguayo Garcia-Rada
• Application Dependency/Limitations of Postgres Version Upgrade
  • From: amitabh kumar
• Re: pgpass hostname and IP address
  • From: Ron Johnson
• Re: pgpass hostname and IP address
  • From: Adrian Klaver
• Re: pgpass hostname and IP address
  • From: Ron Johnson
• Re: pgpass hostname and IP address
  • From: David G. Johnston
• pgpass hostname and IP address
  • From: Ron Johnson
• Need followup setup instructions to postgresql-10.3-1-linux-x64.run
  • From: Sherman Willden
• Re: Ability to create tables
  • From: Ron Johnson
• Re: Ability to create tables
  • From: Tom Lane
• Ability to create tables
  • From: Ron Johnson
• Re: how to get list of sequences owned by a user/role
  • From: Adrian Klaver
• Re: how to get list of sequences owned by a user/role
  • From: Adrian Klaver
• how to get list of sequences owned by a user/role
  • From: Charlin Barak
• Re: ERROR could not access transaction/Could not open file pg_commit_ts
  • From: Jerry Sievers
• Re: ERROR could not access transaction/Could not open file pg_commit_ts
  • From: Alvaro Herrera
• Re: ERROR could not access transaction/Could not open file pg_commit_ts
  • From: Jeremy Finzel
• Re: Feature request: min/max for macaddr type
  • From: Tom Lane
• ERROR could not access transaction/Could not open file pg_commit_ts
  • From: Jeremy Finzel
• Re: pg/tcl performance related
  • From: Tom Lane
• Feature request: min/max for macaddr type
  • From: Herwin Weststrate
• pg/tcl performance related
  • From: wolfgang
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Melvin Davidson
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Aldrin Martoq Ahumada
• Re: Barman versus pgBackRest
  • From: David Steele
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Andre Oliveira Freitas
• Re: Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: David G. Johnston
• Postgresql upgrade to 9.5.12/10.3 changes pg_dump format for cloning schemas
  • From: Aldrin Martoq Ahumada
• Re: Authentication?
  • From: Bjørn T Johansen
• RE: Troubleshooting a segfault and instance crash
  • From: Jan Bilek
• Re: JDBC connectivity issue
  • From: Dave Cramer
• Re: JDBC connectivity issue
  • From: David G. Johnston
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• Re: Prefixing schema name
  • From: Tiffany Thang
• Re: What is the meaning of pg_restore output?
  • From: Tom Lane
• Re: JDBC connectivity issue
  • From: chris
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• Re: JDBC connectivity issue
  • From: Tim Cross
• Re: JDBC connectivity issue
  • From: Adrian Klaver
• JDBC connectivity issue
  • From: chris
• Re: What is the meaning of pg_restore output?
  • From: Adrian Klaver
• Re: circular wait not triggering deadlock ?
  • From: Justin Pryzby
• Re: circular wait not triggering deadlock ?
  • From: Tom Lane
• Re: circular wait not triggering deadlock ?
  • From: Justin Pryzby
• Re: Crash and core on 10.1 and 10.2
  • From: Kelly Burkhart
• Re: circular wait not triggering deadlock ?
  • From: Tom Lane
• Re: Troubleshooting a segfault and instance crash
  • From: Pavel Stehule
• Re: Help troubleshooting SubtransControlLock problems
  • From: Scott Frazer
• circular wait not triggering deadlock ?
  • From: Justin Pryzby
• Re: Troubleshooting a segfault and instance crash
  • From: Blair Boadway
• Re: Troubleshooting a segfault and instance crash
  • From: Pavel Stehule
• Troubleshooting a segfault and instance crash
  • From: Blair Boadway
• Re: What is the meaning of pg_restore output?
  • From: Alexandru Lazarev
• Re: Crash and core on 10.1 and 10.2
  • From: Tom Lane
• Crash and core on 10.1 and 10.2
  • From: Kelly Burkhart
• Re: Trigger to create string to inverse SQL statement
  • From: Francisco Olarte
• Re: Trigger to create string to inverse SQL statement
  • From: Francisco Olarte
• Re: What is the meaning of pg_restore output?
  • From: Adrian Klaver
• Re: Command to execute SQL string
  • From: David G. Johnston
• Re: Trigger to create string to inverse SQL statement
  • From: Łukasz Jarych
• Re: Trigger to create string to inverse SQL statement
  • From: Łukasz Jarych
• Re: Command to execute SQL string
  • From: Łukasz Jarych
• Re: Trigger to create string to inverse SQL statement
  • From: Francisco Olarte
• Re: Command to execute SQL string
  • From: Francisco Olarte
• Trigger to create string to inverse SQL statement
  • From: Łukasz Jarych
• Command to execute SQL string
  • From: Łukasz Jarych
• RE: Resync second slave to new master
  • From: Dylan Luong
• What is the meaning of pg_restore output?
  • From: Alexandru Lazarev
• Re: Resync second slave to new master
  • From: Michael Paquier
• Re: Resync second slave to new master
  • From: Yavuz Selim Sertoğlu
• RE: Resync second slave to new master
  • From: Dylan Luong
• Re: Prefixing schema name
  • From: Achilleas Mantzios
• Replication push instead of pull
  • From: PegoraroF10
• Timescale with replication advice
  • From: geoff hoffman