Postgresql General Discussion

• Thread Index

• FDW and RLS
  • From: Ted Toth
• pg_dump crashes
  • From: Nico De Ranter
• Request to help on GIS Query improvement suggestion.
  • From: postggen2020 s
• Re: Logical replication troubles
  • From: Peter Eisentraut
• btree_gist extension - gbt_cash_union return type
  • From: Tim Kane
• Re: Suggestion to improve query performance of data validation in proc.
  • From: David G. Johnston
• Re: Suggestion to improve query performance of data validation in proc.
  • From: postgann2020 s
• Re: Suggestion to improve query performance of data validation in proc.
  • From: David G. Johnston
• Re: Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Suggestion to improve query performance of data validation in proc.
  • From: postgann2020 s
• Re: Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Re: Query returns no rows in pg_basebackup cluster
  • From: David G. Johnston
• Re: Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Re: Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Re: Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Re: Help understanding SIReadLock growing without bound on completed transaction
  • From: Mike Klaas
• Re: Help understanding SIReadLock growing without bound on completed transaction
  • From: Thomas Munro
• Re: Should I use JSON?
  • From: Tim Cross
• Re: Query returns no rows in pg_basebackup cluster
  • From: Tom Lane
• Re: Query returns no rows in pg_basebackup cluster
  • From: Adrian Klaver
• Re: Query returns no rows in pg_basebackup cluster
  • From: David G. Johnston
• Re: Query returns no rows in pg_basebackup cluster
  • From: Adrian Klaver
• Re: Query returns no rows in pg_basebackup cluster
  • From: Tom Lane
• Re: Query returns no rows in pg_basebackup cluster
  • From: Adrian Klaver
• Re: Table partitioning for cloud service?
  • From: Adrian Klaver
• Re: pg_basebackup + incremental base backups
  • From: Stephen Frost
• Re: Table partitioning for cloud service?
  • From: Ravi Krishna
• Re: Strategy for materialisation and centralisation of data
  • From: Rory Campbell-Lange
• Re: Strategy for materialisation and centralisation of data
  • From: Michael Stephenson
• RE: Should I use JSON?
  • From: Zahir Lalani
• Re: Strategy for materialisation and centralisation of data
  • From: Karsten Hilbert
• Re: Strategy for materialisation and centralisation of data
  • From: Rory Campbell-Lange
• Re: Table partitioning for cloud service?
  • From: Israel Brewster
• Query returns no rows in pg_basebackup cluster
  • From: Andrus
• Re: Table partitioning for cloud service?
  • From: Sándor Daku
• Help understanding SIReadLock growing without bound on completed transaction
  • From: Mike Klaas
• Re: Strategy for materialisation and centralisation of data
  • From: Karsten Hilbert
• Re: Should I use JSON?
  • From: pabloa98
• Re: Table partitioning for cloud service?
  • From: Michael Lewis
• Re: Table partitioning for cloud service?
  • From: Adam Brusselback
• Re: Table partitioning for cloud service?
  • From: Israel Brewster
• Re: Table partitioning for cloud service?
  • From: Christopher Browne
• Re: Table partitioning for cloud service?
  • From: Adrian Klaver
• Re: Should I use JSON?
  • From: David G. Johnston
• Re: Table partitioning for cloud service?
  • From: Israel Brewster
• Re: Should I use JSON?
  • From: Adrian Klaver
• Should I use JSON?
  • From: stan
• Re: Table partitioning for cloud service?
  • From: Adrian Klaver
• Table partitioning for cloud service?
  • From: Israel Brewster
• Re: Suggestion on index creation for TEXT data field
  • From: postgann2020 s
• Re: Suggestion on index creation for TEXT data field
  • From: David G. Johnston
• Re: Suggestion on table analyze
  • From: postgann2020 s
• Re: Suggestion on index creation for TEXT data field
  • From: Adrian Klaver
• Re: Suggestion on index creation for TEXT data field
  • From: postgann2020 s
• Re: Suggestion on table analyze
  • From: Adrian Klaver
• Re: Suggestion on index creation for TEXT data field
  • From: David G. Johnston
• Strategy for materialisation and centralisation of data
  • From: Rory Campbell-Lange
• Re: Behaviour of failed Primary
  • From: Amit Kapila
• Suggestion on index creation for TEXT data field
  • From: postgann2020 s
• Suggestion on table analyze
  • From: postgann2020 s
• Re: pg_basebackup + incremental base backups
  • From: Stephen Frost
• Behaviour of failed Primary
  • From: Santhosh Kumar
• Re: pg_basebackup + incremental base backups
  • From: Christopher Pereira
• Re: How to recover from compressed wal archieve in windows
  • From: Andrus
• Re: How to recover from compressed wal archieve in windows
  • From: Michael Paquier
• Re: How to recover from compressed wal archieve in windows
  • From: Kyotaro Horiguchi
• Re: How to recover from compressed wal archieve in windows
  • From: Paul Förster
• Re: How to recover from compressed wal archieve in windows
  • From: Kyotaro Horiguchi
• Re: How to recover from compressed wal archieve in windows
  • From: Adrian Klaver
• Re: How to recover from compressed wal archieve in windows
  • From: Michael Paquier
• Re: How to recover from compressed wal archieve in windows
  • From: Adrian Klaver
• Re: How to recover from compressed wal archieve in windows
  • From: Adrian Klaver
• Re: SET ROLE and search_path
  • From: Stephen Frost
• Re: SET ROLE and search_path
  • From: Tom Lane
• Re: SET ROLE and search_path
  • From: Patrick FICHE
• Question on removing primary replication node using repmgr?
  • From: Lu, Dan
• Re: SET ROLE and search_path
  • From: Rob Sargent
• Re: SET ROLE and search_path
  • From: Adam Brusselback
• Re: How to recover from compressed wal archieve in windows
  • From: Andrus
• Re: How to recover from compressed wal archieve in windows
  • From: Paul Förster
• Re: How to recover from compressed wal archieve in windows
  • From: Adrian Klaver
• Suggestion to improve query performance.
  • From: postgann2020 s
• Re: SET ROLE and search_path
  • From: Rob Sargent
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Ron
• SET ROLE and search_path
  • From: Patrick FICHE
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Tory M Blue
• Re: PostgreSQLBook
  • From: edavis
• Re: PostgreSQLBook
  • From: Paul Förster
• PostgreSQLBook
  • From: edavis
• Re: Logical replication troubles
  • From: Anders Bøgh Bruun
• How to recover from compressed wal archieve in windows
  • From: Andrus
• Re: Logical replication troubles
  • From: Peter Eisentraut
• Re: A limit clause can cause a poor index choice
  • From: Nick Cleaton
• Re: A limit clause can cause a poor index choice
  • From: Nick Cleaton
• Re: Q: Comparing PostgreSQL and Oracle
  • From: pabloa98
• Re: Q: Comparing PostgreSQL and Oracle
  • From: Steve Baldwin
• RE: Q: Comparing PostgreSQL and Oracle
  • From: Ahmed, Nawaz (Fuji Xerox Australia)
• Re: Q: Comparing PostgreSQL and Oracle
  • From: Pavel Stehule
• Q: Comparing PostgreSQL and Oracle
  • From: Alfonso
• Re: Removing Last field from CSV string
  • From: Samuel Roseman
• Re: Configuring more than one hot standby server
  • From: Kyotaro Horiguchi
• Re: A limit clause can cause a poor index choice
  • From: Mohamed Wael Khobalatte
• Re: A limit clause can cause a poor index choice
  • From: Michael Lewis
• Clarification relation logical replication
  • From: Santhosh Kumar
• Configuring more than one hot standby server
  • From: Santhosh Kumar
• A limit clause can cause a poor index choice
  • From: Nick Cleaton
• Re: Unique index on hash of jsonb value - correct solution?
  • From: Albrecht Dreß
• Re: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Adrian Klaver
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Ron
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Tory M Blue
• Re: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Adrian Klaver
• RE: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Ishan Joshi
• Re: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Adrian Klaver
• RE: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Ishan Joshi
• Re: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Adrian Klaver
• Re: Unique index on hash of jsonb value - correct solution?
  • From: Stephen Frost
• RE: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Ishan Joshi
• Re: idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Adrian Klaver
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Tom Lane
• idle_in_transaction_session_timeout not getting log in PG v12.2
  • From: Ishan Joshi
• Re: Hot and PITR backups in same server
  • From: Andrus
• Re: Huge tables, trying to delete OID's taking 6+hours per table
  • From: Tory M Blue
• Logical replication troubles
  • From: Anders Bøgh Bruun
• Huge tables, trying to delete OID's taking 6+hours per table
  • From: Tory M Blue
• Re: Hot and PITR backups in same server
  • From: Kyotaro Horiguchi
• Re: Unique index on hash of jsonb value - correct solution?
  • From: Laurenz Albe
• Re: template0 needing vacuum freeze?
  • From: Adrian Klaver
• Re: template0 needing vacuum freeze?
  • From: Don Seiler
• Re: template0 needing vacuum freeze?
  • From: Tom Lane
• Re: template0 needing vacuum freeze?
  • From: Don Seiler
• Unique index on hash of jsonb value - correct solution?
  • From: Albrecht Dreß
• Re: Hot and PITR backups in same server
  • From: Andrus
• pg_basebackup: child process exited with error 1
  • From: Ram Pratap Maurya
• Re: Bug on version 12 ?
  • From: Laurenz Albe
• Re: template0 needing vacuum freeze?
  • From: Laurenz Albe
• Re: Hot and PITR backups in same server
  • From: Laurenz Albe
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Removing Last field from CSV string
  • From: Steve Litt
• Re: Inherited an 18TB DB & need to backup
  • From: Steve Litt
• Re: Inherited an 18TB DB & need to backup
  • From: James Sewell
• Re: Using b-tree index for >= condition when joining
  • From: Łukasz Dąbek
• NFS version for replication
  • From: Weatherby,Gerard
• Hot and PITR backups in same server
  • From: Andrus
• Re: Password reset
  • From: Peter J. Holzer
• Password reset
  • From: Jessie Nava
• Re: Inherited an 18TB DB & need to backup
  • From: Ron
• Re: Using b-tree index for >= condition when joining
  • From: Tom Lane
• Re: Ubuntu 20.04: apt.postgresql.org/pub/repos/apt focal-pgdg InRelease' doesn't support architecture 'i386'
  • From: Tim Cross
• Re: Ubuntu 20.04: apt.postgresql.org/pub/repos/apt focal-pgdg InRelease' doesn't support architecture 'i386'
  • From: Thomas Munro
• Re: Ubuntu 20.04: apt.postgresql.org/pub/repos/apt focal-pgdg InRelease' doesn't support architecture 'i386'
  • From: Adrian Klaver
• Ubuntu 20.04: apt.postgresql.org/pub/repos/apt focal-pgdg InRelease' doesn't support architecture 'i386'
  • From: Hugh
• Re: Inherited an 18TB DB & need to backup
  • From: Gavin Flower
• Re: Inherited an 18TB DB & need to backup
  • From: Ron
• Re: Removing Last field from CSV string
  • From: Christian Ramseyer
• Using b-tree index for >= condition when joining
  • From: Łukasz Dąbek
• Re: template0 needing vacuum freeze?
  • From: Don Seiler
• Re: template0 needing vacuum freeze?
  • From: Tom Lane
• Re: Removing Last field from CSV string
  • From: Michael Nolan
• template0 needing vacuum freeze?
  • From: Don Seiler
• Re: Removing Last field from CSV string
  • From: Adrian Klaver
• Re: Removing Last field from CSV string
  • From: PALAYRET Jacques
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Removing Last field from CSV string
  • From: Alex Magnum
• Re: schema agnostic functions in language sql
  • From: David G. Johnston
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Peter J. Holzer
• Re: Circles with circle() vs ST_Buffer() Equality equalities
  • From: PALAYRET Jacques
• Re: Inherited an 18TB DB & need to backup
  • From: Rob Sargent
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Re: Pgpool is crashing when terminating user session
  • From: Tatsuo Ishii
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Pgpool is crashing when terminating user session
  • From: RAJAMOHAN
• Re: Column reset all values
  • From: Peter J. Holzer
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Peter J. Holzer
• Re: Inherited an 18TB DB & need to backup
  • From: Ron
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: schema agnostic functions in language sql
  • From: Tom Lane
• Re: schema agnostic functions in language sql
  • From: Adrian Klaver
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Re: schema agnostic functions in language sql
  • From: Tom Lane
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Re: schema agnostic functions in language sql
  • From: David G. Johnston
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Re: Inherited an 18TB DB & need to backup
  • From: Michael Nolan
• Re: schema agnostic functions in language sql
  • From: Adrian Klaver
• Re: schema agnostic functions in language sql
  • From: Rob Sargent
• Re: schema agnostic functions in language sql
  • From: Adrian Klaver
• schema agnostic functions in language sql
  • From: Rob Sargent
• Re: Inherited an 18TB DB & need to backup
  • From: Ron
• Re: Inherited an 18TB DB & need to backup
  • From: Christophe Pettus
• Unexplained Access Exclusive Locks on Follower from PID7
  • From: Andy Cooper
• Re: Inherited an 18TB DB & need to backup
  • From: Scottix
• Re: Bug on version 12 ?
  • From: Adrian Klaver
• Re: Bug on version 12 ?
  • From: PegoraroF10
• Re: Inherited an 18TB DB & need to backup
  • From: Andreas 'ads' Scherbaum
• Re: Bug on version 12 ?
  • From: Tom Lane
• Re: Bug on version 12 ?
  • From: Adrian Klaver
• Re: Inherited an 18TB DB & need to backup
  • From: Ravi Krishna
• Re: Inherited an 18TB DB & need to backup
  • From: Andreas 'ads' Scherbaum
• Re: Bug on version 12 ?
  • From: John W Higgins
• Re: Bug on version 12 ?
  • From: PegoraroF10
• Re: Bug on version 12 ?
  • From: David G. Johnston
• Re: Bug on version 12 ?
  • From: Tom Lane
• Re: Bug on version 12 ?
  • From: PegoraroF10
• Re: Bug on version 12 ?
  • From: David G. Johnston
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Bug on version 12 ?
  • From: Michael Lewis
• Bug on version 12 ?
  • From: PegoraroF10
• Re: surprisingly slow creation of gist index used in exclude constraint
  • From: Chris Withers
• Re: Inherited an 18TB DB & need to backup
  • From: Gabriele Bartolini
• Re: Inherited an 18TB DB & need to backup
  • From: Ravi Krishna
• Re: PG12.2 Configure cannot enalble SSL
  • From: Gavan Schneider
• Re: PG12.2 Configure cannot enalble SSL
  • From: Gavan Schneider
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Rory Campbell-Lange
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Jan Karremans
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Inherited an 18TB DB & need to backup
  • From: Wolff, Ken L
• Re: Inherited an 18TB DB & need to backup
  • From: Jan Karremans
• Re: PG12.2 Configure cannot enalble SSL
  • From: Tom Lane
• Re: Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: surprisingly slow creation of gist index used in exclude constraint
  • From: Kenneth Marshall
• Re: Inherited an 18TB DB & need to backup
  • From: Christoph Berg
• Re: Inherited an 18TB DB & need to backup
  • From: Rory Campbell-Lange
• Re: Seamless Logical Replication during Fail-over
  • From: Peter Eisentraut
• Re: PG12.2 Configure cannot enalble SSL
  • From: Peter Eisentraut
• Re: PG12.2 Configure cannot enalble SSL
  • From: Gavan Schneider
• Seamless Logical Replication during Fail-over
  • From: Moor Ali
• Circles with circle() vs ST_Buffer() Equality equalities
  • From: PALAYRET Jacques
• Inherited an 18TB DB & need to backup
  • From: Suhail Bamzena
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Laurenz Albe
• Re: surprisingly slow creation of gist index used in exclude constraint
  • From: Chris Withers
• Logical replication for async service communication?
  • From: Sean Huber
• Re: view selection during query rewrite
  • From: Tom Lane
• view selection during query rewrite
  • From: Vamsi Meduri
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Andy Fan
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Michael Lewis
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Virendra Kumar
• Re: surprisingly slow creation of gist index used in exclude constraint
  • From: Tom Lane
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Eduard Rozenberg
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Eduard Rozenberg
• Re: surprisingly slow creation of gist index used in exclude constraint
  • From: ktm
• surprisingly slow creation of gist index used in exclude constraint
  • From: Chris Withers
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Adrian Klaver
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Adrian Klaver
• Re: Practical usage of large objects.
  • From: Thomas Markus
• Re: vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Adrian Klaver
• vacuumdb --jobs deadlock: how to avoid pg_catalog ?
  • From: Eduard Rozenberg
• Re: Reuse an existing slot with a new initdb
  • From: Support
• Re: Practical usage of large objects.
  • From: Laurenz Albe
• Re: Reuse an existing slot with a new initdb
  • From: Tom Lane
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Laurenz Albe
• Re: PG12.2 Configure cannot enalble SSL
  • From: Tom Lane
• Re: Column reset all values
  • From: otar shavadze
• Re: Clarification related to BDR
  • From: Ravi Krishna
• Re: Reuse an existing slot with a new initdb
  • From: Support
• Re: Clarification related to BDR
  • From: Simon Riggs
• Re: pg_upgrade too slow on vacuum phase
  • From: Kouber Saparev
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Andy Fan
• Re: Clarification related to BDR
  • From: Andreas Kretschmer
• Re: Clarification related to BDR
  • From: Magnus Hagander
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Michael Paquier
• Re: Check what has been done for a uncommitted prepared transaction
  • From: Andy Fan
• PG12.2 Configure cannot enalble SSL
  • From: Gavan Schneider
• Sv: Practical usage of large objects.
  • From: Andreas Joseph Krogh
• Check what has been done for a uncommitted prepared transaction
  • From: Andy Fan
• Clarification related to BDR
  • From: Santhosh Kumar
• Reuse an existing slot with a new initdb
  • From: David G. Johnston
• Re: Practical usage of large objects.
  • From: Michael Paquier
• Re: Reuse an existing slot with a new initdb
  • From: Michael Paquier
• Re: Practical usage of large objects.
  • From: Ron
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Adrian Klaver
• Re: Reuse an existing slot with a new initdb
  • From: Support
• Re: Reuse an existing slot with a new initdb
  • From: Support
• Re: Reuse an existing slot with a new initdb
  • From: live-school support
• Re: Reuse an existing slot with a new initdb
  • From: Laurenz Albe
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: Practical usage of large objects.
  • From: Tom Lane
• Practical usage of large objects.
  • From: Dmitry Igrishin
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Adrian Klaver
• Re: Why is it that “aggregate functions are not allowed in FROM clause of their own query level”?
  • From: Tom Lane
• Re: Create user mapping for role
  • From: Tom Lane
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: David Goodenough
• Create user mapping for role
  • From: Gerard Weatherby
• RE: Enforcing uniqueness on [real estate/postal] addresses
  • From: Basques, Bob (CI-StPaul)
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Tom Lane
• RE: Enforcing uniqueness on [real estate/postal] addresses
  • From: Rich Shepard
• Re: Why is it that “aggregate functions are not allowed in FROM clause of their own query level”?
  • From: David G. Johnston
• RE: Enforcing uniqueness on [real estate/postal] addresses
  • From: Basques, Bob (CI-StPaul)
• Re: Reuse an existing slot with a new initdb
  • From: Support
• Re: what is the best way to access cold data on another server?
  • From: Laurenz Albe
• Why is it that “aggregate functions are not allowed in FROM clause of their own query level”?
  • From: Tom Ellis
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Ravi Krishna
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: Column reset all values
  • From: Olivier Gautherot
• Re: Column reset all values
  • From: Peter J. Holzer
• Column reset all values
  • From: otar shavadze
• Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Michael Paquier
• what is the best way to access cold data on another server?
  • From: Amine Tengilimoglu
• Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Mariya Rampurawala
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Kyotaro Horiguchi
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Adrian Klaver
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Tom Lane
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Adrian Klaver
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Rich Shepard
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: TalGloz
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Karsten Hilbert
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Peter Devoy
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Adrian Klaver
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: System column xmin makes anonymity hard
  • From: Francisco Olarte
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• System column xmin makes anonymity hard
  • From: Johannes Linke
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Peter J. Holzer
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Tom Lane
• Re: Hash partitioning, what function is used to compute the hash?
  • From: Michael Lewis
• Re: AutoVacuum and growing transaction XID's
  • From: github kran
• Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Laurenz Albe
• Re: ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Adrian Klaver
• Re: pg_upgrade too slow on vacuum phase
  • From: Adrian Klaver
• ESQL/C: a ROLLBACK rolls back a COMMITED transaction
  • From: Matthias Apitz
• Re: [EXTERNAL] Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Mariya Rampurawala
• pg_upgrade too slow on vacuum phase
  • From: Kouber Saparev
• Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Kyotaro Horiguchi
• Re: create index insist on 2 workers only
  • From: Radoslav Nedyalkov
• Re: PostgreSQL-12 replication failover, pg_rewind fails
  • From: Mariya Rampurawala
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: David G. Johnston
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: David G. Johnston
• Re: Is there a significant difference in Memory settings between 9.5 and 12.
  • From: David G. Johnston
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tom Lane
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Thomas Munro
• Re: Firing an event trigger for ADD COLUMN?
  • From: Michel Pelletier
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: David G. Johnston
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Tim Cross
• Re: Firing an event trigger for ADD COLUMN?
  • From: Alvaro Herrera
• Re: Firing an event trigger for ADD COLUMN?
  • From: Alvaro Herrera
• Re: Firing an event trigger for ADD COLUMN?
  • From: Tanveer Munavar
• Firing an event trigger for ADD COLUMN?
  • From: Michel Pelletier
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: TalGloz
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tom Lane
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Adrian Klaver
• Re: Hash partitioning, what function is used to compute the hash?
  • From: Alvaro Herrera
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tom Lane
• Is there a significant difference in Memory settings between 9.5 and 12
  • From: Tory M Blue
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Peter Devoy
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Paul Jungwirth
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: David G. Johnston
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Adrian Klaver
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: Enforcing uniqueness on [real estate/postal] addresses
  • From: Philip Semanchuk
• Enforcing uniqueness on [real estate/postal] addresses
  • From: Peter Devoy
• Re: Hash partitioning, what function is used to compute the hash?
  • From: Laurenz Albe
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: Hash partitioning, what function is used to compute the hash?
  • From: Michael Lewis
• Hash partitioning, what function is used to compute the hash?
  • From: Dennis Ryan
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• SV: what to log in csvlogs
  • From: Niels Jespersen
• Re: How to restore database to previous state
  • From: David G. Johnston
• RE: How to restore database to previous state
  • From: Ahmed, Nawaz (Fuji Xerox Australia)
• How to restore database to previous state
  • From: Andrus
• Re: Best way to use trigger to email a report ?
  • From: Rory Campbell-Lange
• Re: what to log in csvlogs
  • From: Adrian Klaver
• what to log in csvlogs
  • From: Mary Johnson
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• PostgreSQL-12 replication failover, pg_rewind fails
  • From: Mariya Rampurawala
• Re: Best way to use trigger to email a report ?
  • From: AC Gomez
• Re: Best way to use trigger to email a report ?
  • From: Tim Clarke
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Support
• Re: import .sql file into PostgreSQL database
  • From: Michael Paquier
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Paul Förster
• Re: Best way to use trigger to email a report ?
  • From: Tim Cross
• Re: Best way to use trigger to email a report ?
  • From: Magnus Hagander
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: Fehrle, Brian
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Adrian Klaver
• Re: AutoVacuum and growing transaction XID's
  • From: Michael Lewis
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: David G. Johnston
• Reuse an existing slot with a new initdb
  • From: Support
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: David G. Johnston
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Support
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: David G. Johnston
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Adrian Klaver
• Re: Memory footprint diff between 9.5 and 12
  • From: Tory M Blue
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: Fehrle, Brian
• Re: Thoughts on how to avoid a massive integer update.
  • From: Fehrle, Brian
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Support
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• Re: pg_restore V12 fails consistently against piped pg_dumps
  • From: Mohamed Wael Khobalatte
• Re: pg_basebackup cannot compress to STDOUNT
  • From: Adrian Klaver
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• pg_basebackup cannot compress to STDOUNT
  • From: Support
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Tory M Blue
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Tory M Blue
• Re: Best way to use trigger to email a report ?
  • From: David Gauthier
• Re: Best way to use trigger to email a report ?
  • From: David G. Johnston
• Re: Thoughts on how to avoid a massive integer update.
  • From: David G. Johnston
• Re: Best way to use trigger to email a report ?
  • From: David G. Johnston
• Re: Best way to use trigger to email a report ?
  • From: Christophe Pettus
• Re: Best way to use trigger to email a report ?
  • From: Alan Hodgson
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: Fehrle, Brian
• Best way to use trigger to email a report ?
  • From: David Gauthier
• Re: pg_restore V12 fails consistently against piped pg_dumps
  • From: Adrian Klaver
• Re: pg_temp schema created while using DB Link
  • From: Adrian Klaver
• Re: pg_temp schema created while using DB Link
  • From: Thomas Kellerer
• Re: pg_temp schema created while using DB Link
  • From: Jill Jade
• Re: import .sql file into PostgreSQL database
  • From: Gaurav
• Re: pg_restore V12 fails consistently against piped pg_dumps
  • From: Laurenz Albe
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Laurenz Albe
• Re: Memory footprint diff between 9.5 and 12
  • From: Laurenz Albe
• Re: pg_temp schema created while using DB Link
  • From: Laurenz Albe
• Re: AutoVacuum and growing transaction XID's
  • From: github kran
• pg_temp schema created while using DB Link
  • From: Jill Jade
• Re: AutoVacuum and growing transaction XID's
  • From: github kran
• Question correct Way to switch Slave to master
  • From: Hauke Homburg
• Re: AutoVacuum and growing transaction XID's
  • From: David Rowley
• Re: AutoVacuum and growing transaction XID's
  • From: David Rowley
• Re: AutoVacuum and growing transaction XID's
  • From: github kran
• Re: walreceiver termination
  • From: Kyotaro Horiguchi
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: David Rowley
• Re: Memory footprint diff between 9.5 and 12
  • From: Alan Hodgson
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: David G. Johnston
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Tom Lane
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: David G. Johnston
• Re: AutoVacuum and growing transaction XID's
  • From: github kran
• Memory footprint diff between 9.5 and 12
  • From: Tory M Blue
• Re: pg_dump negation regex
  • From: Eudald Valcàrcel Lacasa
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Virendra Kumar
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Adrian Klaver
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Tory M Blue
• Re: pg_dump negation regex
  • From: Rob Sargent
• Re: Odd postgres12 upgrade is changing or munging a password?
  • From: Adrian Klaver
• Re: pg_dump negation regex
  • From: Eudald Valcàrcel Lacasa
• Odd postgres12 upgrade is changing or munging a password?
  • From: Tory M Blue
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Amarendra Konda
• Re: AutoVacuum and growing transaction XID's
  • From: Michael Lewis
• AutoVacuum and growing transaction XID's
  • From: github kran
• Re: increase of xact_commit vs txid_current
  • From: Julien Rouhaud
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Amarendra Konda
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Amarendra Konda
• Re: pg_dump negation regex
  • From: Adrian Klaver
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Amarendra Konda
• Re: Lock Postgres account after X number of failed logins?
  • From: Christian Ramseyer
• increase of xact_commit vs txid_current
  • From: reg_pg_stefanz
• pg_dump negation regex
  • From: Eudald Valcàrcel Lacasa
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Adrian Klaver
• Re: wal_sender_timeout default
  • From: Adrian Klaver
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Michael Lewis
• Re: wal_sender_timeout default
  • From: David G. Johnston
• Re: wal_sender_timeout default
  • From: Adrian Klaver
• Re: wal_sender_timeout default
  • From: Michael Lewis
• Re: Postgres 11.6-2 to 11.7 worth the upgrade?
  • From: David G. Johnston
• Re: Postgres 11.6-2 to 11.7 worth the upgrade?
  • From: Michael Lewis
• Postgres 11.6-2 to 11.7 worth the upgrade?
  • From: Jasen Lentz
• wal_sender_timeout default
  • From: Jasen Lentz
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: David G. Johnston
• Re: New Role drop with Grant/Revokes stop working after subsequent runs
  • From: Stephen Frost
• Re: Lock Postgres account after X number of failed logins?
  • From: Stephen Frost
• Re: pg_restore V12 fails consistently against piped pg_dumps
  • From: Mohamed Wael Khobalatte
• RE: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ashish Chugh
• Re: Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Adrian Klaver
• RE: pg_basebackup inconsistent performance
  • From: Jasen Lentz
• Explain plan changes - IN CLAUSE ( Passing direct values Vs INNER Query )
  • From: Amarendra Konda
• Could not launch new process for connection: Could not allocate memory
  • From: Lisandro Rostagno
• Re: pg_restore V12 fails consistently against piped pg_dumps
  • From: Tom Lane
• pg_restore V12 fails consistently against piped pg_dumps
  • From: Mohamed Wael Khobalatte
• Re: New Role drop with Grant/Revokes stop working after subsequent runs
  • From: David G. Johnston
• New Role drop with Grant/Revokes stop working after subsequent runs
  • From: AC Gomez
• Re: Lock Postgres account after X number of failed logins?
  • From: Geoff Winkless
• previous replication slot and new initdb
  • From: Support
• Re: White space affecting parsing of range values
  • From: Thom Brown
• Re: White space affecting parsing of range values
  • From: Thom Brown
• Re: White space affecting parsing of range values
  • From: Tom Lane
• Re: White space affecting parsing of range values
  • From: Adrian Klaver
• Re: pg_basebackup inconsistent performance
  • From: Stephen Frost
• Re: White space affecting parsing of range values
  • From: Thom Brown
• Re: White space affecting parsing of range values
  • From: Adrian Klaver
• RE: pg_basebackup inconsistent performance
  • From: Jasen Lentz
• White space affecting parsing of range values
  • From: Thom Brown
• Re: Lock Postgres account after X number of failed logins?
  • From: Stephen Frost
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ravi Krishna
• Re: Lock Postgres account after X number of failed logins?
  • From: Magnus Hagander
• Re: Lock Postgres account after X number of failed logins?
  • From: Peter J. Holzer
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ravi Krishna
• Re: pg_basebackup inconsistent performance
  • From: Adrian Klaver
• Re: pg_basebackup inconsistent performance
  • From: Adrian Klaver
• RE: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ram Pratap Maurya
• Re: EXTERNAL: Re: Lock Postgres account after X number of failed logins?
  • From: Stephen Frost
• RE: EXTERNAL: Re: Lock Postgres account after X number of failed logins?
  • From: Wolff, Ken L
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Michael Lewis
• Re: Encoding conversion: Use replacement character instead of failing query with "ERROR: character with byte sequence 0xd0 0xad in encoding "UTF8" has no equivalent in encoding LATIN1" ?
  • From: Christian Ramseyer
• Re: Lock Postgres account after X number of failed logins?
  • From: Stephen Frost
• pg_basebackup inconsistent performance
  • From: Jasen Lentz
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Christian Ramseyer
• Re: Lock Postgres account after X number of failed logins?
  • From: Tim Cross
• Re: Lock Postgres account after X number of failed logins?
  • From: Guillaume Lelarge
• Re: Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ravi Krishna
• Abnormal Growth of Index Size - Index Size 3x large than table size.
  • From: Ram Pratap Maurya
• Re: Lock Postgres account after X number of failed logins?
  • From: Paul Förster
• Re: Lock Postgres account after X number of failed logins?
  • From: Geoff Winkless
• Re: Lock Postgres account after X number of failed logins?
  • From: Christian Ramseyer
• Re: Wrong PostgreSQL Plan
  • From: Virendra Kumar
• Re: Temporary table has become problematically persistent
  • From: Ricky Ramirez
• Re: Wrong PostgreSQL Plan
  • From: David G. Johnston
• Wrong PostgreSQL Plan
  • From: Virendra Kumar
• Re: Encoding conversion: Use replacement character instead of failing query with "ERROR: character with byte sequence 0xd0 0xad in encoding "UTF8" has no equivalent in encoding LATIN1" ?
  • From: Tom Lane
• Re: Lock Postgres account after X number of failed logins?
  • From: Tim Cross
• Encoding conversion: Use replacement character instead of failing query with "ERROR: character with byte sequence 0xd0 0xad in encoding "UTF8" has no equivalent in encoding LATIN1" ?
  • From: Christian Ramseyer
• Re: Lock Postgres account after X number of failed logins?
  • From: Wolff, Ken L
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: Lock Postgres account after X number of failed logins?
  • From: Stephen Frost
• Re: RETURNING to_jsonb(...)
  • From: Adrian Klaver
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• RETURNING to_jsonb(...)
  • From: Miles Elam
• Re: Thoughts on how to avoid a massive integer update.
  • From: Peter J. Holzer
• Re: Lock Postgres account after X number of failed logins?
  • From: Tom Lane
• Re: 12.2: Howto check memory-leak in worker?
  • From: Peter
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: Lock Postgres account after X number of failed logins?
  • From: Wolff, Ken L
• Re: jsonb unique constraints
  • From: Ted Toth
• Re: 12.2: Howto check memory-leak in worker?
  • From: Tom Lane
• Re: Installing Postgis25_11
  • From: Clifford Snow
• Re: jsonb unique constraints
  • From: David G. Johnston
• Re: Installing Postgis25_11
  • From: Adrian Klaver
• jsonb unique constraints
  • From: Ted Toth
• Re: Installing Postgis25_11
  • From: Clifford Snow
• Re: Lock Postgres account after X number of failed logins?
  • From: Allan Kamau
• Re: Lock Postgres account after X number of failed logins?
  • From: Adrian Klaver
• Lock Postgres account after X number of failed logins?
  • From: Wolff, Ken L
• Re: 12.2: Howto check memory-leak in worker?
  • From: Peter
• Re: Migration from Oracle to Postgres
  • From: legrand legrand
• Re: Installing Postgis25_11
  • From: Laurenz Albe
• Re: How to know if initial sync of logical subscription is finished
  • From: Laurenz Albe
• Re: How to know if initial sync of logical subscription is finished
  • From: Klaus Darilion
• Re: Migration from Oracle to Postgres
  • From: Paul Förster
• Migration from Oracle to Postgres
  • From: Jean Claude
• Re: COPY blocking \dt+?
  • From: David Rowley
• Re: COPY blocking \dt+?
  • From: pinker
• Re: COPY blocking \dt+?
  • From: David Rowley
• Re: Temporary table has become problematically persistent
  • From: Jerry Sievers
• COPY blocking \dt+?
  • From: pinker
• Re: Installing Postgis25_11
  • From: Virendra Kumar
• Re: Temporary table has become problematically persistent
  • From: Ricky Ramirez
• Re: Temporary table has become problematically persistent
  • From: Tom Lane
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Installing Postgis25_11
  • From: Clifford Snow
• Temporary table has become problematically persistent
  • From: Ricky Ramirez
• Re: 12.2: Howto check memory-leak in worker?
  • From: Thomas Munro
• Re: 12.2: Howto check memory-leak in worker?
  • From: Peter
• Re: Thoughts on how to avoid a massive integer update.
  • From: Rob Sargent
• Re: Thoughts on how to avoid a massive integer update.
  • From: Adrian Klaver
• Thoughts on how to avoid a massive integer update.
  • From: Fehrle, Brian
• Re: 12.2: Howto check memory-leak in worker?
  • From: Adrian Klaver
• Re: 12.2: Howto check memory-leak in worker?
  • From: Dilip Kumar
• Re: walreceiver termination
  • From: Justin King
• 12.2: Howto check memory-leak in worker?
  • From: Peter
• Re: Clustered Index in PG
  • From: Laurenz Albe
• Re: Transition tables for column-specific UPDATE triggers
  • From: Thomas Munro
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: TalGloz
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: TalGloz
• Re: Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: Adrian Klaver
• Upgrade Process Says "The database server was not shut down cleanly" but it was
  • From: TalGloz
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Peter J. Holzer
• RE: Re: Very frequent "Too many clients" eventually crashes postmaster
  • From: Abraham, Danny
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Very frequent "Too many clients" eventually crashes postmaster
  • From: Adrian Klaver
• Re: Very frequent "Too many clients" eventually crashes postmaster
  • From: Tom Lane
• Very frequent "Too many clients" eventually crashes postmaster
  • From: Abraham, Danny
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Tom Lane
• Clustered Index in PG
  • From: brajmohan saxena
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Andrew Gierth
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Tom Lane
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: Compiling C Extension Functions against PostgreSQL 12
  • From: Adrian Klaver
• Compiling C Extension Functions against PostgreSQL 12
  • From: TalGloz
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Adrian Klaver
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Matthias Apitz
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: David G. Johnston
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: Adrian Klaver
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Adrian Klaver
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Adrian Klaver
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Matthias Apitz
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Matthias Apitz
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: TalGloz
• Re: How to use pg_waldump?
  • From: Alvaro Herrera
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: Adrian Klaver
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: TalGloz
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: Bruce Momjian
• Re: Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: Adrian Klaver
• Checking for Presence of Required Libraries Fails during PostgreSQL Upgrade
  • From: TalGloz
• Re: Pgbackrest restore options
  • From: David Steele
• Re: How to use pg_waldump?
  • From: Paul Förster
• RE: How to use pg_waldump?
  • From: André Hänsel
• Re: How to use pg_waldump?
  • From: Paul Förster
• RE: How to use pg_waldump?
  • From: André Hänsel
• Re: How to use pg_waldump?
  • From: Paul Förster
• RE: How to use pg_waldump?
  • From: André Hänsel
• Re: How to use pg_waldump?
  • From: Paul Förster
• How to use pg_waldump?
  • From: André Hänsel
• Re: pg_stat_statements : how to catch non successfully finished statements ?
  • From: legrand legrand
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Matthias Apitz
• Re: How to move a 11.4 cluster to another Linux host, but empty?
  • From: Paul Förster
• How to move a 11.4 cluster to another Linux host, but empty?
  • From: Matthias Apitz
• Re: pg_stat_statements : how to catch non successfully finished statements ?
  • From: Tom Lane
• Re: pg_stat_statements : how to catch non successfully finished statements ?
  • From: legrand legrand
• Re: Detecting renamed columns via pgouput in logical replication ?
  • From: Alvaro Herrera
• Re: script libraries?
  • From: Thomas Kellerer
• Re: script libraries?
  • From: Pavel Stehule
• script libraries?
  • From: Chris Stephens
• Re: Mixed Locales and Upgrading
  • From: Tom Lane
• Re: Mixed Locales and Upgrading
  • From: Adrian Klaver
• Re: Mixed Locales and Upgrading
  • From: Don Seiler
• Re: Why is a check constraint not working ?
  • From: David G. Johnston
• Why is a check constraint not working ?
  • From: David Gauthier
• Regarding db performance improvement
  • From: Durgamahesh Manne
• Re: GIN Expression Indexes
  • From: Adrian Klaver
• GIN Expression Indexes
  • From: Taylor Sarrafian
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: How to debug "background worker "parallel worker" (PID 32152) was terminated by signal 11: Segmentation fault"
  • From: Mahendra Singh Thalor
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: HOST variable in psql
  • From: Paul Förster
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: HOST variable in psql
  • From: Tom Lane
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: HOST variable in psql
  • From: Paul Förster
• Re: PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Tom Lane
• Re: How to debug "background worker "parallel worker" (PID 32152) was terminated by signal 11: Segmentation fault"
  • From: Tom Lane
• PostgreSQL client hangs sometimes on 'EXEC SQL PREPARE sid_sisisinst FROM :select_anw;'
  • From: Matthias Apitz
• Re: HOST variable in psql
  • From: Tom Lane
• Re: PostgreSQL Server version compatibility check with Window 2016
  • From: Magnus Hagander
• How to debug "background worker "parallel worker" (PID 32152) was terminated by signal 11: Segmentation fault"
  • From: Radu Radutiu
• HOST variable in psql
  • From: Paul Förster
• Re: Detecting renamed columns via pgouput in logical replication ?
  • From: David G. Johnston
• Re: Detecting renamed columns via pgouput in logical replication ?
  • From: David G. Johnston
• Re: Detecting renamed columns via pgouput in logical replication ?
  • From: Andreas Andreakis
• Re: Detecting renamed columns via pgouput in logical replication ?
  • From: David G. Johnston
• Re: Binary downloads and upgrading the host OS
  • From: Tom Browder
• Re: Binary downloads and upgrading the host OS
  • From: Magnus Hagander
• Re: Triggers and Full Text Search *
  • From: Malik Rumi
• Re: Binary downloads and upgrading the host OS
  • From: Tom Browder
• Re: Binary downloads and upgrading the host OS
  • From: Adrian Klaver
• Binary downloads and upgrading the host OS
  • From: Tom Browder
• Re: create index insist on 2 workers only
  • From: Peter Geoghegan
• Re: psql \copy
  • From: Ron
• Re: psql \copy
  • From: Steve Clark
• Re: psql \copy
  • From: Rob Sargent
• Re: psql \copy
  • From: Adrian Klaver
• Re: psql \copy
  • From: Steve Clark
• Re: psql \copy
  • From: Steve Crawford
• Re: psql \copy
  • From: David G. Johnston
• Re: psql \copy
  • From: Adrian Klaver
• psql \copy
  • From: Steve Clark
• create index insist on 2 workers only
  • From: Radoslav Nedyalkov
• Re: Weird behaviour of C extension function
  • From: Laurenz Albe
• Weird behaviour of C extension function
  • From: Amaury Bouchard
• Re: Can I tell libpq to connect to the primary?
  • From: Michael Paquier
• Re: Reg: Help to understand the source code
  • From: Preethi S
• Re: Fw: Re: Re: Could Not Connect To Server
  • From: Rob Sargent
• Fw: Re: Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Ned to understand why all the idle connections
  • From: Si Chen
• Re: Fw: Re: Could Not Connect To Server
  • From: Rob Sargent
• Re: Fw: Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Fw: Re: Could Not Connect To Server
  • From: David G. Johnston
• Re: Fw: Re: Could Not Connect To Server
  • From: Adrian Klaver
• Re: Fw: Re: Could Not Connect To Server
  • From: Dummy Account
• Re: walreceiver termination
  • From: Justin King
• Re: Fw: Re: Could Not Connect To Server
  • From: Rob Sargent
• RE: how to slow down parts of Pg
  • From: Kevin Brannen
• Re: Ned to understand why all the idle connections
  • From: David G. Johnston
• Re: Fw: Re: Could Not Connect To Server
  • From: Adrian Klaver
• RE: how to slow down parts of Pg
  • From: Kevin Brannen
• Re: Ned to understand why all the idle connections
  • From: Si Chen
• Re: Question on banner display after PG initial connection
  • From: David G. Johnston
• Question on banner display after PG initial connection
  • From: Lu, Dan
• Re: Fw: Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Fw: Re: Could Not Connect To Server
  • From: Adrian Klaver
• Fw: Re: Could Not Connect To Server
  • From: Dummy Account
• Re: walreceiver termination
  • From: Tom Lane
• Re: walreceiver termination
  • From: Justin King
• Re: walreceiver termination
  • From: Justin King
• Re: Could Not Connect To Server
  • From: Adrian Klaver
• Re: Could Not Connect To Server
  • From: Rob Sargent
• Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Could Not Connect To Server
  • From: Adrian Klaver
• Re: Could Not Connect To Server
  • From: Rob Sargent
• Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Ned to understand why all the idle connections
  • From: David G. Johnston
• Re: Could Not Connect To Server
  • From: David G. Johnston
• Re: Ned to understand why all the idle connections
  • From: David Gauthier
• Re: Could Not Connect To Server
  • From: Dummy Account
• Re: Ned to understand why all the idle connections
  • From: David G. Johnston
• Ned to understand why all the idle connections
  • From: David Gauthier
• Re: Could Not Connect To Server
  • From: David G. Johnston
• Could Not Connect To Server
  • From: Dummy Account
• Re: walreceiver termination
  • From: Tom Lane
• Re: Reg: Help to understand the source code
  • From: Paul Jungwirth
• Re: relationship of backend_start, query_start, state_change
  • From: David G. Johnston
• walreceiver termination
  • From: Justin King
• Re: relationship of backend_start, query_start, state_change
  • From: David G. Johnston
• Re: relationship of backend_start, query_start, state_change
  • From: Olivier Gautherot
• Re: relationship of backend_start, query_start, state_change
  • From: David G. Johnston
• Re: relationship of backend_start, query_start, state_change
  • From: Olivier Gautherot
• Re: relationship of backend_start, query_start, state_change
  • From: Michael Lewis
• Re: Reg: Help to understand the source code
  • From: Preethi S
• relationship of backend_start, query_start, state_change
  • From: Si Chen
• Re: Reg: Help to understand the source code
  • From: Rob Sargent
• Re: Reg: Help to understand the source code
  • From: Preethi S
• Re: Reg: Help to understand the source code
  • From: Adrian Klaver
• Reg: Help to understand the source code
  • From: Preethi S
• Re: parameter limit
  • From: Scott Ribe
• [no subject]
  • From: servetturan
• Re: parameter limit
  • From: David G. Johnston
• Re: parameter limit
  • From: Adrian Klaver
• parameter limit
  • From: Scott Ribe
• Re: pg11: Query using index, but only for half the partitions
  • From: Michael Lewis
• Re: pg11: Query using index, but only for half the partitions
  • From: Andreas Kretschmer
• Re: pg11: Query using index, but only for half the partitions
  • From: Stefan Knecht
• Re: pg11: Query using index, but only for half the partitions
  • From: Andreas Kretschmer
• pg11: Query using index, but only for half the partitions
  • From: Stefan Knecht
• Re: Can I tell libpq to connect to the primary?
  • From: Christian Ramseyer
• Re: How do work tercile, percentile & funcion percentile_cont() ?
  • From: Peter J. Holzer
• Re: how to slow down parts of Pg
  • From: Peter J. Holzer
• Can I tell libpq to connect to the primary?
  • From: Christian Ramseyer
• Re: how to slow down parts of Pg
  • From: Ron
• PG based ETL tools
  • From: brajmohan saxena
• Re: how to slow down parts of Pg
  • From: Adrian Klaver
• RE: how to slow down parts of Pg
  • From: Kevin Brannen
• Re: How do work tercile, percentile & funcion percentile_cont() ?
  • From: Tom Lane