Postgresql General Discussion

• Thread Index

• Re: ID column naming convention
  • From: Karsten Hilbert
• Re: question
  • From: Guillaume Lelarge
• Re: ID column naming convention
  • From: Gavin Flower
• Re: problems with copy from file
  • From: Jim Nasby
• Re: ID column naming convention
  • From: Jim Nasby
• Re: using postgresql for session
  • From: Jim Nasby
• Re: pgpool ssl handshake failure
  • From: Tatsuo Ishii
• Re: Standby pg_dump Conflict with Recovery
  • From: Louis Battuello
• Re: Standby pg_dump Conflict with Recovery
  • From: Adrian Klaver
• Standby pg_dump Conflict with Recovery
  • From: Louis Battuello
• Re: postgres function
  • From: Torsten Förtsch
• Re: question
  • From: Adrian Klaver
• Re: question
  • From: Melvin Davidson
• Re: question
  • From: Scott Mead
• Re: question
  • From: Melvin Davidson
• Re: question
  • From: Guillaume Lelarge
• Re: postgres function
  • From: Ramesh T
• Re: question
  • From: anj patnaik
• Re: postgres function
  • From: David G. Johnston
• Re: Simple way to load xml into table
  • From: David G. Johnston
• Re: Simple way to load xml into table
  • From: Rob Sargent
• Simple way to load xml into table
  • From: Emi
• Re: pgpool ssl handshake failure
  • From: Adrian Klaver
• Re: pgpool ssl handshake failure
  • From: AI Rumman
• Re: Installing plpython3u
  • From: Dario Beraldi
• Re: Installing plpython3u
  • From: Dario Beraldi
• Re: Installing plpython3u
  • From: Tom Lane
• Re: postgres function
  • From: David G. Johnston
• Re: question
  • From: Melvin Davidson
• Re: Installing plpython3u
  • From: Adrian Klaver
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: David G. Johnston
• Re: postgres function
  • From: Geoff Winkless
• Re: question
  • From: Adrian Klaver
• Re: postgres function
  • From: Joe Conway
• Re: Installing plpython3u
  • From: Adrian Klaver
• Re: postgres function
  • From: Ramesh T
• Re: postgres function
  • From: Ramesh T
• question
  • From: anj patnaik
• Re: Installing plpython3u
  • From: Dario Beraldi
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: Rob Richardson
• Re: Installing plpython3u
  • From: Dario Beraldi
• Cast hstore type to bytea (and later to hex possibly)
  • From: Igor Stassiy
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: Rob Richardson
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: Rob Richardson
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: Tim Clarke
• Re: Installing plpython3u
  • From: Adrian Klaver
• Re: How can I use crosstab functons in PostgreSQL 9.3?
  • From: Tom Lane
• Re: pgpool ssl handshake failure
  • From: Adrian Klaver
• Re: Installing plpython3u
  • From: Tom Lane
• How can I use crosstab functons in PostgreSQL 9.3?
  • From: Rob Richardson
• Re: Installing plpython3u
  • From: Dario Beraldi
• pgpool ssl handshake failure
  • From: AI Rumman
• Re: Installing plpython3u
  • From: Tom Lane
• Re: Installing plpython3u
  • From: Dario Beraldi
• Re: Installing plpython3u
  • From: Adrian Klaver
• Re: postgres function
  • From: David G. Johnston
• Installing plpython3u
  • From: Dario Beraldi
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Olivier Dony
• Re: Understanding "seq scans"
  • From: Lele Gaifax
• Re: How to get the session user in a C user defined function
  • From: Michael Paquier
• How to get the session user in a C user defined function
  • From: John Leiseboer
• Re: Not storing MD5 hashed passwords
  • From: Jeff Janes
• Re: using postgresql for session
  • From: Tiger Nassau
• Re: Not storing MD5 hashed passwords
  • From: Michael Paquier
• Re: Not storing MD5 hashed passwords
  • From: Quiroga, Damian
• Re: Not storing MD5 hashed passwords
  • From: Jeff Janes
• Re: Not storing MD5 hashed passwords
  • From: Joshua D. Drake
• BDR: pg_stat_bdr: cache lookup failed
  • From: Selim Tuvi
• Re: Not storing MD5 hashed passwords
  • From: John R Pierce
• Not storing MD5 hashed passwords
  • From: Quiroga, Damian
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Gavin Flower
• Re: postgres function
  • From: David G. Johnston
• Re: using postgresql for session
  • From: Jonathan Vanasco
• postgres function
  • From: Ramesh T
• problems with copy from file
  • From: Andreas Kretschmer
• Re: Understanding "seq scans"
  • From: Merlin Moncure
• Re: ID column naming convention
  • From: Karsten Hilbert
• Re: Creating Report for PieChart
  • From: dinesh kumar
• Re: Creating Report for PieChart
  • From: Scott Mead
• Re: Creating Report for PieChart
  • From: Scott Mead
• Re: Creating Report for PieChart
  • From: Bruce Momjian
• Creating Report for PieChart
  • From: Alex Magnum
• Re: ID column naming convention
  • From: John R Pierce
• Re: ID column naming convention
  • From: droberts
• Archiving while idle every archive_timeout with wal_level hot_standby
  • From: Laurence Rowe
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: ID column naming convention
  • From: Gavin Flower
• FOSDEM 2016, 30th and 31st January 2016, Brussels: Call for Participation
  • From: Stefan Keller
• Re: Merge join vs merge semi join against primary key
  • From: Sean Rhea
• Re: Merge join vs merge semi join against primary key
  • From: Tom Lane
• Re: Merge join vs merge semi join against primary key
  • From: Sean Rhea
• Re: ID column naming convention
  • From: David G. Johnston
• Re: Understanding "seq scans"
  • From: Lele Gaifax
• Re: ID column naming convention
  • From: Rob Sargent
• ID column naming convention
  • From: droberts
• Re: Understanding "seq scans"
  • From: Alvaro Herrera
• Re: hanged session on index creation
  • From: Tom Lane
• hanged session on index creation
  • From: Mikhail
• hanged session on index creation
  • From: Mikhail
• Re: Understanding "seq scans"
  • From: Lele Gaifax
• Re: Understanding "seq scans"
  • From: Lele Gaifax
• Re: BDR: no free replication state could be found
  • From: Craig Ringer
• Re: BDR workers exiting?
  • From: Craig Ringer
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Victor Blomqvist
• Re: Understanding "seq scans"
  • From: Merlin Moncure
• Re: Merge join vs merge semi join against primary key
  • From: David Rowley
• Re: Pattern match against array elements?
  • From: Israel Brewster
• Re: Understanding "seq scans"
  • From: Alvaro Herrera
• Re: Understanding "seq scans"
  • From: Lele Gaifax
• Re: Understanding "seq scans"
  • From: Adrian Klaver
• Re: Understanding "seq scans"
  • From: Kevin Grittner
• Re: Pattern match against array elements?
  • From: Jeff Janes
• Understanding "seq scans"
  • From: Lele Gaifax
• Re: Pattern match against array elements?
  • From: Israel Brewster
• Re: Pattern match against array elements?
  • From: Israel Brewster
• Re: Constraint allowing value up to 2 times but no more than 2 times
  • From: Jim Nasby
• Re: Pattern match against array elements?
  • From: Tom Lane
• Re: Pattern match against array elements?
  • From: Jeff Janes
• Re: Pattern match against array elements?
  • From: dinesh kumar
• Pattern match against array elements?
  • From: Israel Brewster
• Re: Effecient time ranges in 9.4/9.5?
  • From: Karsten Hilbert
• Re: Effecient time ranges in 9.4/9.5?
  • From: Jim Nasby
• Re: Constraint allowing value up to 2 times but no more than 2 times
  • From: Jim Nasby
• Constraint allowing value up to 2 times but no more than 2 times
  • From: Dara Unglaube
• Re: BDR workers exiting?
  • From: Steve Pribyl
• Re: Merge join vs merge semi join against primary key
  • From: Igor Neyman
• Re: Merge join vs merge semi join against primary key
  • From: Igor Neyman
• Re: BDR workers exiting?
  • From: Steve Pribyl
• Re: BDR workers exiting?
  • From: Andres Freund
• Re: BDR workers exiting?
  • From: Jim Nasby
• Re: BDR workers exiting?
  • From: Jim Nasby
• Re: Left Join with Limit 1
  • From: Jim Nasby
• Re: Left Join with Limit 1
  • From: Paul Jungwirth
• Left Join with Limit 1
  • From: Alex Magnum
• BDR workers exiting?
  • From: Steve Pribyl
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Jim Nasby
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Tom Lane
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Andres Freund
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Andres Freund
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Andres Freund
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Steve Petrie, P.Eng.
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Daniel Verite
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Albe Laurenz
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Steve Petrie, P.Eng.
• Re: checkpoints anatomy
  • From: Achilleas Mantzios
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: rob stone
• checkpoints anatomy
  • From: Richardson Hinestroza
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Victor Blomqvist
• Re: There can be only one
  • From: Andreas Kretschmer
• Re: There can be only one
  • From: Andreas Kretschmer
• There can be only one
  • From: Jason Dusek
• Re: Trouble setting up replication
  • From: Chuck Martin
• Re: Trouble setting up replication
  • From: Adrian Klaver
• Re: *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Adrian Klaver
• Re: Trouble setting up replication
  • From: John R Pierce
• Re: Trouble setting up replication
  • From: Chuck Martin
• *** QUESTION *** After successful 'BEGIN;' command -- why PGSQL_TRANSACTION_ACTIVE and not PGSQL_TRANSACTION_INTRANS?
  • From: Steve Petrie, P.Eng.
• Re: Merge join vs merge semi join against primary key
  • From: Jeremy Harris
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Victor Blomqvist
• Re: Best practices for aggregate table design
  • From: John R Pierce
• Re: Best practices for aggregate table design
  • From: Roxanne Reid-Bennett
• Re: Best practices for aggregate table design
  • From: droberts
• Re: Merge join vs merge semi join against primary key
  • From: Sean Rhea
• Merge join vs merge semi join against primary key
  • From: Sean Rhea
• Re: BDR: no free replication state could be found
  • From: Selim Tuvi
• Re: Best way to sync table DML between databases
  • From: Francisco Reyes
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Albe Laurenz
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Albe Laurenz
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Adrian Klaver
• Re: Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Bill Moran
• Re: Version management for extensions
  • From: Albe Laurenz
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Drop or alter column under load give ERROR #42804 structure of query does not match function result type:
  • From: Victor Blomqvist
• Re: BDR: no free replication state could be found
  • From: Craig Ringer
• BDR: no free replication state could be found
  • From: Selim Tuvi
• Version management for extensions
  • From: Jeff Janes
• Re: Best practices for aggregate table design
  • From: David G. Johnston
• Re: Best practices for aggregate table design
  • From: droberts
• Re: blank in query - cannot return results
  • From: David G. Johnston
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: blank in query - cannot return results
  • From: Adrian Klaver
• Re: blank in query - cannot return results
  • From: Emi
• blank in query - cannot return results
  • From: Emi
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Alvaro Herrera
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Adrian Klaver
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: Issues with german locale on CentOS 5,6,7
  • From: Daniel Verite
• Re: Best practices for aggregate table design
  • From: Vick Khera
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: Best practices for aggregate table design
  • From: hari . fuchs
• Re: Best practices for aggregate table design
  • From: Thomas Kellerer
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: Issues with german locale on CentOS 5,6,7
  • From: Peter Geoghegan
• Re: Issues with german locale on CentOS 5,6,7
  • From: Peter Geoghegan
• Re: Issues with german locale on CentOS 5,6,7
  • From: Tom Lane
• Re: Issues with german locale on CentOS 5,6,7
  • From: Thomas Munro
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: Issues with german locale on CentOS 5,6,7
  • From: Peter Geoghegan
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: Issues with german locale on CentOS 5,6,7
  • From: Thomas Munro
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: Best practices for aggregate table design
  • From: droberts
• Re: backup.old
  • From: Scott Mead
• Re: How to drop user if objects depend on it
  • From: Tom Lane
• Re: backup.old
  • From: David G. Johnston
• Re: backup.old
  • From: Steve Pribyl
• Re: Best practices for aggregate table design
  • From: Marc Mamin
• Re: backup.old
  • From: David G. Johnston
• PostGIS 2.2.0 Released
  • From: Paul Ramsey
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: backup.old
  • From: Steve Pribyl
• Re: backup.old
  • From: David G. Johnston
• Re: backup.old
  • From: Steve Pribyl
• Re: How to drop user if objects depend on it
  • From: Tom Lane
• Re: using postgresql for session
  • From: Rob Sargent
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: md5(large_object_id)
  • From: Jim Nasby
• Re: Try to understand VACUUM and its settings
  • From: Jim Nasby
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Jim Nasby
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: How to drop user if objects depend on it
  • From: Adrian Klaver
• Re: using postgresql for session
  • From: Adrian Klaver
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: using postgresql for session
  • From: Bill Moran
• Re: Issues with german locale on CentOS 5,6,7
  • From: Peter Geoghegan
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: Ynt: How to drop user if objects depend on it
  • From: Jerry Sievers
• Re: How to drop user if objects depend on it
  • From: Tom Lane
• Re: How to drop user if objects depend on it
  • From: Melvin Davidson
• using postgresql for session
  • From: john.tiger
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: How to drop user if objects depend on it
  • From: Tom Lane
• Re: How to drop user if objects depend on it
  • From: Melvin Davidson
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: How to drop user if objects depend on it
  • From: Melvin Davidson
• Re: How to drop user if objects depend on it
  • From: Adrian Klaver
• Re: Issues with german locale on CentOS 5,6,7
  • From: Tom Lane
• Re: How to drop user if objects depend on it
  • From: Andrus
• Re: How to drop user if objects depend on it
  • From: Thom Brown
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Re: md5(large_object_id)
  • From: Pavel Stehule
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Ynt: How to drop user if objects depend on it
  • From: Neslisah Demirci
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• How to drop user if objects depend on it
  • From: Andrus
• Re: Issues with german locale on CentOS 5,6,7
  • From: Thomas Kellerer
• Re: Issues with german locale on CentOS 5,6,7
  • From: Bernd Helmle
• Re: Issues with german locale on CentOS 5,6,7
  • From: Peter Geoghegan
• Issues with german locale on CentOS 5,6,7
  • From: Bernd Helmle
• Re: backup.old
  • From: Steve Pribyl
• Re: backup.old
  • From: John R Pierce
• backup.old
  • From: Steve Pribyl
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Tom Lane
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Adrian Klaver
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Adrian Klaver
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: dubious optimization of the function in SELECT INTO target list
  • From: Adrian Klaver
• dubious optimization of the function in SELECT INTO target list
  • From: Oleksii Kliukin
• Re: Best practices for aggregate table design
  • From: David G. Johnston
• Re: Best practices for aggregate table design
  • From: droberts
• Re: Best practices for aggregate table design
  • From: David G. Johnston
• Re: Best practices for aggregate table design
  • From: John R Pierce
• Re: Best practices for aggregate table design
  • From: droberts
• Re: Recording exceptions within function (autonomous transactions?)
  • From: John R Pierce
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Olivier Dony
• Re: Processing data from table using awk.
  • From: John McKown
• Re: Best practices for aggregate table design
  • From: David G. Johnston
• Best practices for aggregate table design
  • From: droberts
• Re: [pgsql-es-ayuda] No funciona WITH con mas de 2 sentencias DML
  • From: Alvaro Herrera
• Re: Processing data from table using awk.
  • From: Basques, Bob (CI-StPaul)
• No funciona WITH con mas de 2 sentencias DML
  • From: Hellmuth Vargas
• Re: BDR Rejoin of failed node, hangs.
  • From: Steve Pribyl
• Re: Processing data from table using awk.
  • From: John McKown
• Re: Processing data from table using awk.
  • From: Reid Thompson
• Re: Processing data from table using awk.
  • From: David G. Johnston
• Re: Processing data from table using awk.
  • From: David G. Johnston
• Re: Processing data from table using awk.
  • From: Melvin Davidson
• Re: Recording exceptions within function (autonomous transactions?)
  • From: Tom Lane
• Processing data from table using awk.
  • From: John McKown
• Re: How to reduce pg_dump backup time
  • From: Scott Mead
• Re: How to reduce pg_dump backup time
  • From: Adrian Klaver
• Re: Recording exceptions within function (autonomous transactions?)
  • From: Adrian Klaver
• Re: md5(large_object_id)
  • From: Daniel Verite
• Re: How to reduce pg_dump backup time
  • From: Scott Mead
• Re: [Q] Serializable
  • From: Kevin Grittner
• Re: Recording exceptions within function (autonomous transactions?)
  • From: Scott Mead
• Recording exceptions within function (autonomous transactions?)
  • From: Steve Pritchard
• Re: Selecting pairs of numbers
  • From: Albe Laurenz
• Re: BDR Rejoin of failed node, hangs.
  • From: Craig Ringer
• Re: Selecting pairs of numbers
  • From: Charles Clavadetscher
• How to reduce pg_dump backup time
  • From: Sachin Srivastava
• Re: to_number, to_char inconsistency.
  • From: Bruce Momjian
• Re: Getting a leading zero on negative intervals with to_char?
  • From: Bruce Momjian
• Re: Selecting pairs of numbers
  • From: Adrian Klaver
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: Replication with 9.4
  • From: Thomas Munro
• Try to understand VACUUM and its settings
  • From: Michael Chau
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Kevin Grittner
• Re: Database size on disk
  • From: dinesh kumar
• Database size on disk
  • From: Quiroga, Damian
• Re: postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: Selecting pairs of numbers
  • From: Raymond O'Donnell
• Re: Selecting pairs of numbers
  • From: Raymond O'Donnell
• Re: Selecting pairs of numbers
  • From: Adrian Klaver
• Re: Selecting pairs of numbers
  • From: John McKown
• Re: Selecting pairs of numbers
  • From: Raymond O'Donnell
• Re: Selecting pairs of numbers
  • From: Igor Neyman
• Re: Selecting pairs of numbers
  • From: Adrian Klaver
• Re: Selecting pairs of numbers
  • From: Chris Mair
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Selecting pairs of numbers
  • From: Raymond O'Donnell
• Re: postgres standby won't start
  • From: Adrian Klaver
• Re: postgres standby won't start
  • From: Andreas Kretschmer
• postgres standby won't start
  • From: Ramalingam, Sankarakumar
• Re: BDR Rejoin of failed node, hangs.
  • From: Steve Pribyl
• Re: md5(large_object_id)
  • From: Kevin Grittner
• Re: Unexpected query result
  • From: dinesh kumar
• Re: Best way to sync table DML between databases
  • From: jimbosworth
• Re: Unexpected query result
  • From: Begin Daniel
• Re: Best way to sync table DML between databases
  • From: Bill Moran
• Best way to sync table DML between databases
  • From: jimbosworth
• Re: Unexpected query result
  • From: Adrian Klaver
• Unexpected query result
  • From: Begin Daniel
• Re: postgresql doesn't start
  • From: Adrian Klaver
• Re: postgresql doesn't start
  • From: Adrian Klaver
• Re: Effecient time ranges in 9.4/9.5?
  • From: Karsten Hilbert
• Re: Replication with 9.4
  • From: Madovsky
• Re: Replication with 9.4
  • From: Michael Paquier
• Re: postgresql doesn't start
  • From: Paolo De Michele
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Emre Hasegeli
• Re: Replication with 9.4
  • From: Michael Paquier
• Re: BEGIN, END & ROLLBACK commands -- do they produce a SQLSTATE value?
  • From: Adrian Klaver
• Re: BEGIN, END & ROLLBACK commands -- do they produce a SQLSTATE value?
  • From: Steve Petrie, P.Eng.
• Re: Replication with 9.4
  • From: Madovsky
• Re: BEGIN, END & ROLLBACK commands -- do they produce a SQLSTATE value?
  • From: rob stone
• Re: Replication with 9.4
  • From: Michael Paquier
• Re: Replication with 9.4
  • From: Madovsky
• Re: postgresql doesn't start
  • From: Adrian Klaver
• Re: Replication with 9.4
  • From: Madovsky
• Re: postgresql doesn't start
  • From: Paolo De Michele
• Re: Replication with 9.4
  • From: Edson Richter
• *** CORRECTION -- PLEASE IGNORE *** BEGIN, END & ROLLBACK commands -- do they produce a SQLSTATE value?
  • From: Steve Petrie, P.Eng.
• BEGIN, END & ROLLBACK commands -- do they produce a SQLSTATE value?
  • From: Steve Petrie, P.Eng.
• Re: Replication with 9.4
  • From: Michael Paquier
• Replication with 9.4
  • From: Madovsky
• Re: postgresql doesn't start
  • From: Nicolas Paris
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: David G. Johnston
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Dane Foster
• Re: Sensitivity to drive failure?
  • From: Peter Geoghegan
• Re: "global" & shared sequences
  • From: Jim Nasby
• Re: aggregates, distinct, order by, and case - why won't this work
  • From: David G. Johnston
• Re: postgresql doesn't start
  • From: John R Pierce
• Re: postgresql doesn't start
  • From: Adrian Klaver
• Re: postgresql doesn't start
  • From: John R Pierce
• Re: postgresql doesn't start
  • From: Tom Lane
• Re: "global" & shared sequences
  • From: Jonathan Vanasco
• Re: aggregates, distinct, order by, and case - why won't this work
  • From: Tom Lane
• postgresql doesn't start
  • From: Paolo De Michele
• aggregates, distinct, order by, and case - why won't this work
  • From: David G. Johnston
• Re: Broken primary key after backup restore.
  • From: Kevin Grittner
• Re: "global" & shared sequences
  • From: Jim Nasby
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Jim Nasby
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Kevin Grittner
• Re: Postgresql 9.4 and ZFS?
  • From: Jim Nasby
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Olivier Dony
• Re: Sensitivity to drive failure?
  • From: Tom Lane
• Sensitivity to drive failure?
  • From: Israel Brewster
• Re: Effecient time ranges in 9.4/9.5?
  • From: Tom Lane
• Effecient time ranges in 9.4/9.5?
  • From: Steven Lembark
• Re: Postgresql 9.4 and ZFS?
  • From: Joseph Kregloh
• "global" & shared sequences
  • From: Jonathan Vanasco
• Re: Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Jim Nasby
• Re: BDR Rejoin of failed node, hangs.
  • From: Alvaro Herrera
• Re: BDR Rejoin of failed node, hangs.
  • From: Jim Nasby
• Re: Postgresql 9.4 and ZFS?
  • From: Jim Nasby
• BDR Rejoin of failed node, hangs.
  • From: Steve Pribyl
• Re: Postgresql 9.4 and ZFS?
  • From: Joseph Kregloh
• Re: Postgresql 9.4 and ZFS?
  • From: Keith Fiske
• Re: Postgresql 9.4 and ZFS?
  • From: Benjamin Smith
• Re: Postgresql 9.4 and ZFS?
  • From: Benjamin Smith
• Re: Postgresql 9.4 and ZFS?
  • From: Tomas Vondra
• Re: Postgresql 9.4 and ZFS?
  • From: Tomas Vondra
• Re: Postgresql 9.4 and ZFS?
  • From: Keith Fiske
• Re: Postgresql 9.4 and ZFS?
  • From: Benjamin Smith
• Re: Postgresql 9.4 and ZFS?
  • From: Patric Bechtel
• Re: Postgresql 9.4 and ZFS?
  • From: Tomas Vondra
• Re: Postgresql 9.4 and ZFS?
  • From: Tomas Vondra
• Re: Postgresql 9.4 and ZFS?
  • From: Jov
• Re: Postgresql 9.4 and ZFS?
  • From: Patric Bechtel
• Re: Postgresql 9.4 and ZFS?
  • From: John R Pierce
• Re: Postgresql 9.4 and ZFS?
  • From: Larry Rosenman
• Re: Postgresql 9.4 and ZFS?
  • From: Benjamin Smith
• Re: Format
  • From: Ramesh T
• Re: Format
  • From: Adrian Klaver
• Re: Postgresql 9.4 and ZFS?
  • From: John R Pierce
• Re: 9.4 and centos/yum multiversion installs
  • From: John R Pierce
• Postgresql 9.4 and ZFS?
  • From: Benjamin Smith
• 9.4 and centos/yum multiversion installs
  • From: John R Pierce
• Re: pg_restore fails to restore sequences
  • From: Spencer Gardner
• Re: Format
  • From: Ramesh T
• Re: pgpgout/s without swapping--what does it mean?
  • From: rahulraveendran
• Serialization errors despite KEY SHARE/NO KEY UPDATE
  • From: Olivier Dony
• Re: WAL Shipping and streaming replication
  • From: hubert depesz lubaczewski
• Re: Format
  • From: Andreas Joseph Krogh
• Re: Format
  • From: Igor Neyman
• Re: pg_restore fails to restore sequences
  • From: Alvaro Herrera
• Re: pg_restore fails to restore sequences
  • From: Tom Lane
• Re: pg_restore fails to restore sequences
  • From: Thom Brown
• Re: pg_restore fails to restore sequences
  • From: Spencer Gardner
• Re: pg_restore fails to restore sequences
  • From: Thom Brown
• Re: pg_restore fails to restore sequences
  • From: Tom Lane
• pg_restore fails to restore sequences
  • From: Spencer Gardner
• Re: Format
  • From: David G. Johnston
• Re: Format
  • From: David G. Johnston
• Re: Format
  • From: Igor Neyman
• Re: WAL Shipping and streaming replication
  • From: Scott Marlowe
• Re: Format
  • From: David G. Johnston
• Format
  • From: Ramesh T
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Vincent Veyron
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Vincent Veyron
• Re: WAL Shipping and streaming replication
  • From: hubert depesz lubaczewski
• Re: WAL Shipping and streaming replication
  • From: Keith Fiske
• Re: WAL Shipping and streaming replication
  • From: Scott Marlowe
• WAL Shipping and streaming replication
  • From: CS DBA
• Re: Extract giving wrong week of year
  • From: Ben Primrose
• Re: Listen/notify, equivalents on other DBs
  • From: Mark Morgan Lloyd
• Re: issue, dumping and restoring tables with table inheritance can alter column order
  • From: Michael Paquier
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Jim Nasby
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Tom Lane
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Adrian Klaver
• Re: Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Jim Nasby
• Re: error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Jim Nasby
• error on CREATE INDEX when restoring from dump file: could not read block 0
  • From: Vincent Veyron
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: Server-side hooks for user session start and session end
  • From: David G. Johnston
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Tom Lane
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Tom Lane
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Re: Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: Server-side hooks for user session start and session end
  • From: Pavel Stehule
• Server-side hooks for user session start and session end
  • From: Nikolai Zhubr
• Re: How to speed up delete where not in
  • From: Melvin Davidson
• Re: How to speed up delete where not in
  • From: David Rowley
• How to speed up delete where not in
  • From: Andrus
• Re: Listen/notify, equivalents on other DBs
  • From: Thomas Kellerer
• Re: Test failover for PosgreSql 9.2
  • From: Francisco Reyes
• Listen/notify, equivalents on other DBs
  • From: Mark Morgan Lloyd
• Re: Extract giving wrong week of year
  • From: Tom Lane
• Extract giving wrong week of year
  • From: Ben Primrose
• Re: to pg
  • From: Igor Neyman
• Test failover for PosgreSql 9.2
  • From: yuryu
• Re: Automatically Updatable Foreign Key Views
  • From: Raymond Brinzer
• Re: Postgresql HA questions
  • From: Israel Brewster
• Re: to pg
  • From: Tom Lane
• Re: to pg
  • From: Alban Hertroys
• Re: Dropped connections with pg_basebackup
  • From: Francisco Reyes
• Re: Dropped connections with pg_basebackup
  • From: Francisco Reyes
• Re: to pg
  • From: Albe Laurenz
• Re: to pg
  • From: Ladislav Lenart
• to pg
  • From: Ramesh T
• Re: to pg
  • From: Geoff Winkless
• Re: Postgresql HA questions
  • From: Steve Pritchard
• Re: Use tar to online backup has an error
  • From: maxiangqian
• Re: Dropped connections with pg_basebackup
  • From: Sherrylyn Branchaw
• Re: Dropped connections with pg_basebackup
  • From: Alvaro Herrera
• Re: Dropped connections with pg_basebackup
  • From: Adrian Klaver
• Re: Dropped connections with pg_basebackup
  • From: Sherrylyn Branchaw
• Dropped connections with pg_basebackup
  • From: Francisco Reyes
• Re: [Q] Serializable
  • From: David G. Johnston
• [Q] Serializable
  • From: Ladislav Lenart
• Re: epoch and timezone changed bevior
  • From: Willy-Bas Loos
• Re: epoch and timezone changed bevior
  • From: Adrian Klaver
• Re: epoch and timezone changed bevior
  • From: Tom Lane
• Re: epoch and timezone changed bevior
  • From: Tom Lane
• Re: epoch and timezone changed bevior
  • From: Adrian Klaver
• Re: epoch and timezone changed bevior
  • From: Adrian Klaver
• Re: Automatically Updatable Foreign Key Views
  • From: Tom Lane
• Re: Use tar to online backup has an error
  • From: David Steele
• Re: Use tar to online backup has an error
  • From: Stephen Frost
• Re: Use tar to online backup has an error
  • From: David Steele
• Re: epoch and timezone changed bevior
  • From: Willy-Bas Loos
• Re: epoch and timezone changed bevior
  • From: Willy-Bas Loos
• Re: epoch and timezone changed bevior
  • From: Adrian Klaver
• Re: epoch and timezone changed bevior
  • From: Vik Fearing
• Re: Convert number to string
  • From: Francisco Olarte
• epoch and timezone changed bevior
  • From: Willy-Bas Loos
• Re: Use tar to online backup has an error
  • From: Yves Dorfsman
• Re: Convert number to string
  • From: Melvin Davidson
• Re: Grant SELECT/Execute to View/Function but not underlying Table
  • From: David G. Johnston
• Re: Grant SELECT/Execute to View/Function but not underlying Table
  • From: Thom Brown
• Re: Grant SELECT/Execute to View/Function but not underlying Table
  • From: David G. Johnston
• Re: Grant SELECT/Execute to View/Function but not underlying Table
  • From: Maxim Boguk
• Grant SELECT/Execute to View/Function but not underlying Table
  • From: Alex Magnum
• Use tar to online backup has an error
  • From: maxiangqian
• Fwd: Convert number to string
  • From: Francisco Olarte
• Re: Convert number to string
  • From: John R Pierce
• Convert number to string
  • From: Hengky Liwandouw
• Re: Automatically Updatable Foreign Key Views
  • From: David Rowley
• Automatically Updatable Foreign Key Views
  • From: Raymond Brinzer
• Re: pgcrypto
  • From: Jeff Janes
• Re: OR vs UNION vs UNION ALL
  • From: Merlin Moncure
• pgcrypto
  • From: Ramesh T
• Re: Table using more disk space than expected
  • From: Francisco Olarte
• Re: Table using more disk space than expected
  • From: Steve Pritchard
• Re: Table using more disk space than expected
  • From: Jimit Amin
• Re: Table using more disk space than expected
  • From: Tom Lane
• Table using more disk space than expected
  • From: Steve Pritchard
• Postgresql HA questions
  • From: Israel Brewster
• Re: The curious case of two inserts, a shrinking xmax, and a ShareLock on transaction
  • From: Jeff Dik
• PostgreSQL and Windows 10 upgrade
  • From: Daniel Begin
• Re: The curious case of two inserts, a shrinking xmax, and a ShareLock on transaction
  • From: Alvaro Herrera
• Re: numeric data type
  • From: Juan Pablo L.
• Re: The curious case of two inserts, a shrinking xmax, and a ShareLock on transaction
  • From: Jeff Dik
• OR vs UNION vs UNION ALL
  • From: Etienne Champetier
• Re: Advise on memory usage limitation by PostgreSQL on Windows
  • From: Daniel Begin
• Re: The curious case of two inserts, a shrinking xmax, and a ShareLock on transaction
  • From: Alvaro Herrera
• The curious case of two inserts, a shrinking xmax, and a ShareLock on transaction
  • From: Jeff Dik
• Advise on memory usage limitation by PostgreSQL on Windows
  • From: Venkata Balaji N
• Re: Inject rows into query resultes
  • From: David G. Johnston
• Inject rows into query resultes
  • From: Alex Magnum
• Re: numeric data type
  • From: Alvaro Herrera
• Re: numeric data type
  • From: Juan Pablo L.
• Re: numeric data type
  • From: Alvaro Herrera
• Re: numeric data type
  • From: Juan Pablo L.
• Re: numeric data type
  • From: Tom Lane
• numeric data type
  • From: Juan Pablo L.
• Re: Queuing query
  • From: Steve Crawford
• Re: how to show time zone with numerical offset in CSV log?
  • From: Adrian Klaver
• Re: Queuing query
  • From: Jeff Janes
• Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
  • From: Maycon Oliveira
• Re: pgsql-95 repo in rsync
  • From: Kjetil Nygård
• Re: how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: how to show time zone with numerical offset in CSV log?
  • From: Tom Lane
• Re: how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
  • From: Tom Lane
• Re: md5(large_object_id)
  • From: Karsten Hilbert
• Re: how to show time zone with numerical offset in CSV log?
  • From: Adrian Klaver
• pg_dump - postgre 9.2 and "server closed the connection unexpectedly"
  • From: Maycon Oliveira
• Re: md5(large_object_id)
  • From: Willy-Bas Loos
• Re: how to show time zone with numerical offset in CSV log?
  • From: Adrian Klaver
• Re: how to show time zone with numerical offset in CSV log?
  • From: Tom Lane
• could not load library liblwgeom-2.1.7.so
  • From: Willy-Bas Loos
• Re: how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: how to show time zone with numerical offset in CSV log?
  • From: Charles Clavadetscher
• Re: how to show time zone with numerical offset in CSV log?
  • From: Adrian Klaver
• Re: how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: pgpass (in)flexibility
  • From: Peter Eisentraut
• Re: pgsql-95 repo in rsync
  • From: Devrim GÜNDÜZ
• Re: how to show time zone with numerical offset in CSV log?
  • From: Charles Clavadetscher
• how to show time zone with numerical offset in CSV log?
  • From: Michael Zoet
• Re: pgsql-95 repo in rsync
  • From: Devrim GÜNDÜZ
• Re: pgsql-95 repo in rsync
  • From: Devrim GÜNDÜZ
• Re: Broken primary key after backup restore.
  • From: Michael Chau
• Re: pgsql-95 repo in rsync
  • From: John R Pierce
• Queuing query
  • From: Steve Crawford
• Re: pgsql-95 repo in rsync
  • From: Adrian Klaver
• md5(large_object_id)
  • From: Karsten Hilbert
• Re: postgres 9.3
  • From: Melvin Davidson
• Re: postgres 9.3
  • From: Alvaro Herrera
• Re: postgres 9.3
  • From: John R Pierce
• Re: postgres 9.3
  • From: Melvin Davidson
• pgsql-95 repo in rsync
  • From: Kjetil Nygård
• Re: Memory for BYTEA returned by C function is not released until connection is dropped
  • From: Pavel Stehule
• Memory for BYTEA returned by C function is not released until connection is dropped
  • From: John Leiseboer
• postgres 9.3
  • From: Ramesh T
• Re: @ operator
  • From: Igor Neyman
• Re: @ operator
  • From: Bushmelev Anton
• Re: looking for old rpm
  • From: Etienne Champetier
• Re: looking for old rpm
  • From: John McKown
• Re: looking for old rpm
  • From: John R Pierce
• Re: Rounding Float Array
  • From: Chris Mair
• Re: Rounding Float Array
  • From: Andreas Kretschmer
• Re: Rounding Float Array
  • From: hubert depesz lubaczewski
• Re: Rounding Float Array
  • From: Andreas Kretschmer
• Re: Rounding Float Array
  • From: Chris Mair
• Rounding Float Array
  • From: Alex Magnum
• Re: looking for old rpm
  • From: Devrim GÜNDÜZ
• looking for old rpm
  • From: Etienne Champetier
• Re: Memory for BYTEA returned by C function is not released until connection is dropped
  • From: John Leiseboer
• Re: Memory for BYTEA returned by C function is not released until connection is dropped
  • From: Tom Lane
• Memory for BYTEA returned by C function is not released until connection is dropped
  • From: John Leiseboer
• Re: clone_schema function
  • From: Melvin Davidson
• Re: Can somebody explain what is the meaning for HashAggregate?
  • From: Bill Moran
• Can somebody explain what is the meaning for HashAggregate?
  • From: lin
• numeric
  • From: Juan Pablo L.
• Re: Multiple insert
  • From: Adrian Klaver
• Re: Multiple insert
  • From: Adrian Klaver
• Re: Multiple insert
  • From: James Keener
• Multiple insert
  • From: FarjadFarid(ChkNet)
• Re: Broken primary key after backup restore.
  • From: David Steele
• Re: Broken primary key after backup restore.
  • From: Michael Chau
• Re: clone_schema function
  • From: Melvin Davidson
• Re: Broken primary key after backup restore.
  • From: Jeff Janes
• Re: search_path not reloaded via unix socket connections
  • From: Kong Man
• Re: search_path not reloaded via unix socket connections
  • From: Adrian Klaver
• Re: search_path not reloaded via unix socket connections
  • From: Kong Man
• Re: Broken primary key after backup restore.
  • From: Adrian Klaver
• Re: Delete trigger
  • From: Leif Jensen
• Re: Delete trigger
  • From: David G. Johnston
• Re: Delete trigger
  • From: Ioana Danes
• Re: Online backup of PostgreSQL data.
  • From: Sathiyan Subramanian
• Re: Delete trigger
  • From: Leif Jensen
• Re: Delete trigger
  • From: Albe Laurenz
• Re: Delete trigger
  • From: Leif Jensen
• Re: Delete trigger
  • From: Charles Clavadetscher
• Delete trigger
  • From: Leif Jensen
• Re: Broken primary key after backup restore.
  • From: Guillaume Lelarge
• Re: BDR: cannot drop database even after parting the node
  • From: Craig Ringer
• Re: BDR truncate and replication sets
  • From: Craig Ringer
• Re: search_path not reloaded via unix socket connections
  • From: Tom Lane
• Re: search_path not reloaded via unix socket connections
  • From: David G. Johnston
• Re: Broken primary key after backup restore.
  • From: Adrian Klaver
• Re: search_path not reloaded via unix socket connections
  • From: Tom Lane
• Re: search_path not reloaded via unix socket connections
  • From: David G. Johnston
• Re: search_path not reloaded via unix socket connections
  • From: David G. Johnston
• Re: search_path not reloaded via unix socket connections
  • From: Tom Lane
• Re: Hiding name and version
  • From: Quiroga, Damian
• search_path not reloaded via unix socket connections
  • From: Kong Man
• Re: Hiding name and version
  • From: Jerry Sievers
• Re: Broken primary key after backup restore.
  • From: Michael Chau
• Re: Broken primary key after backup restore.
  • From: Adrian Klaver
• Broken primary key after backup restore.
  • From: Michael Chau
• Re: BDR: cannot drop database even after parting the node
  • From: Florin Andrei
• Re: Hiding name and version
  • From: Tom Lane
• Re: Hiding name and version
  • From: Tom Lane
• Re: Hiding name and version
  • From: Quiroga, Damian
• Re: Hiding name and version
  • From: Joshua D. Drake
• Re: Import Problem
  • From: Adrian Klaver
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Tom Lane
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Alvaro Herrera
• Re: @ operator
  • From: David G. Johnston
• Hiding name and version
  • From: Quiroga, Damian
• Re: @ operator
  • From: John McKown
• Re: @ operator
  • From: David G. Johnston
• @ operator
  • From: Антон Бушмелев
• Re: Import Problem
  • From: Ramesh T
• Re: Import Problem
  • From: Ramesh T
• Re: clone_schema function
  • From: Marc Mamin
• Re: BDR truncate and replication sets
  • From: Alvaro Herrera
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Marc Mamin
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Adrian Klaver
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Tom Lane
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Adrian Klaver
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Tom Lane
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Adrian Klaver
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: David G. Johnston
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Tom Lane
• Re: clone_schema function
  • From: Melvin Davidson
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: pinker
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: David G. Johnston
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Adrian Klaver
• Re: Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: Albe Laurenz
• Shouldn't "WHEN (OLD.* IS DISTINCT FROM NEW.*)" clause be independent from data type?
  • From: pinker
• Re: Online backup of PostgreSQL data.
  • From: Albe Laurenz
• Re: Online backup of PostgreSQL data.
  • From: John R Pierce
• Online backup of PostgreSQL data.
  • From: Raman, Karthik IN BLR STS
• Re: BDR truncate and replication sets
  • From: Sylvain MARECHAL
• Re: Import Problem
  • From: Venkata Balaji N
• Re: BDR problem
  • From: Florin Andrei
• Re: BDR: cannot drop database even after parting the node
  • From: Florin Andrei
• BDR: cannot drop database even after parting the node
  • From: Florin Andrei
• Re: Import Problem
  • From: Rob Sargent
• Import Problem
  • From: Ramesh T
• Re: pgpass (in)flexibility
  • From: Jim Nasby
• Re: BDR: cannot remove node from group
  • From: Florin Andrei
• Re: BDR: cannot remove node from group
  • From: Florin Andrei
• Re: clone_schema function
  • From: Igor Neyman
• Re: clone_schema function
  • From: Igor Neyman
• Re: [BUGS] BUG #13619: regression functions return Null
  • From: Biswadeep Banerjee
• Re: BDR truncate and replication sets
  • From: Alvaro Herrera
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: David G. Johnston
• Re: clone_schema function
  • From: Melvin Davidson
• Re: pgpass (in)flexibility
  • From: Ben Chobot
• Re: Exclusively locking parent tables while disinheriting children.
  • From: Thom Brown
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Melvin Davidson
• Multiple Update queries
  • From: sri harsha
• BDR truncate and replication sets
  • From: Sylvain MARECHAL
• Re: Materialized View or table?
  • From: Jim Nasby
• Re: pgpass (in)flexibility
  • From: Jim Nasby
• Re: clone_schema function
  • From: Jim Nasby
• Materialized View or table?
  • From: Johann Spies
• Re: avoid lock conflict between SELECT and TRUNCATE
  • From: Jim Nasby
• pgpass (in)flexibility
  • From: Ben Chobot
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Jim Nasby
• Re: issue, dumping and restoring tables with table inheritance can alter column order
  • From: Jim Nasby
• Re: BDR problem
  • From: Martín Marqués
• Re: [BUGS] BUG #13619: regression functions return Null
  • From: David G. Johnston
• Re: issue, dumping and restoring tables with table inheritance can alter column order
  • From: David G. Johnston
• Re: Ubuntu installed postgresql password failure
  • From: Jan de Visser
• issue, dumping and restoring tables with table inheritance can alter column order
  • From: Ingmar Brouns
• Re: GIN Trigram Index Size
  • From: Francisco Olarte
• Re: Ubuntu installed postgresql password failure
  • From: Jan de Visser
• Re: GIN Trigram Index Size
  • From: Christian Ramseyer
• Re: Ubuntu installed postgresql password failure
  • From: Martín Marqués
• Re: BDR problem
  • From: Craig Ringer
• Re: BDR problem
  • From: Giovanni Maruzzelli
• Re: Ubuntu installed postgresql password failure
  • From: John R Pierce
• Re: Ubuntu installed postgresql password failure
  • From: Jan de Visser
• Re: Ubuntu installed postgresql password failure
  • From: Adrian Klaver
• Re: Ubuntu installed postgresql password failure
  • From: Adrian Klaver
• Ubuntu installed postgresql password failure
  • From: Dale Seaburg
• Re: Forced external sort?
  • From: Tomas Vondra
• Re: Forced external sort?
  • From: Jeff Janes
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Daniel Verite
• Re: clone_schema function
  • From: Igor Neyman
• BDR problem
  • From: Charles Lynch
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: David G. Johnston
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Daniel Verite
• Re: clone_schema function
  • From: Alvaro Herrera
• Forced external sort?
  • From: rolf
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Alvaro Herrera
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Alvaro Herrera
• Re: clone_schema function
  • From: Melvin Davidson
• Re: Domains, check_violation and undefined column field in error
  • From: David G. Johnston
• Domains, check_violation and undefined column field in error
  • From: Andri Möll
• Re: avoid lock conflict between SELECT and TRUNCATE
  • From: Sridhar N Bamandlapally
• Re: avoid lock conflict between SELECT and TRUNCATE
  • From: Venkata Balaji N
• Re: Very puzzling sort behavior
  • From: Ken Tanzer
• Re: Very puzzling sort behavior
  • From: Joe Conway
• Re: Very puzzling sort behavior
  • From: Andrew Sullivan
• Re: Very puzzling sort behavior
  • From: Ken Tanzer
• Re: Very puzzling sort behavior
  • From: Alvaro Herrera
• Re: Very puzzling sort behavior
  • From: Ken Tanzer
• Re: Very puzzling sort behavior
  • From: Ken Tanzer
• Re: Very puzzling sort behavior
  • From: Peter Geoghegan
• Re: Very puzzling sort behavior
  • From: Ken Tanzer
• Re: Very puzzling sort behavior
  • From: Tom Lane
• Re: Very puzzling sort behavior
  • From: Steve Crawford
• Re: Very puzzling sort behavior
  • From: Peter Geoghegan
• Very puzzling sort behavior
  • From: Ken Tanzer
• Re: BDR mailing list
  • From: Joshua D. Drake
• BDR mailing list (was: Error when installing the bdr extension)
  • From: Martín Marqués
• Error when installing the bdr extension
  • From: Ioana Danes
• Re: clone_schema function
  • From: Melvin Davidson
• Re: clone_schema function
  • From: Igor Neyman
• Can I integrate PostgreSQL into MS Visual Studio EXPRESS ?
  • From: Denis Yanov
• Re: Bugs with like_option in CREATE TABLE
  • From: Melvin Davidson
• Re: Bugs with like_option in CREATE TABLE
  • From: hubert depesz lubaczewski
• Re: GIN Trigram Index Size
  • From: Jeff Janes
• Re: Bugs with like_option in CREATE TABLE
  • From: Melvin Davidson
• Re: Bugs with like_option in CREATE TABLE
  • From: David G. Johnston
• Bugs with like_option in CREATE TABLE
  • From: Melvin Davidson