Postgresql General Discussion

• Thread Index

• Re: Average New Users Per DOW
  • From: David G. Johnston
• Re: Average New Users Per DOW
  • From: Robert DiFalco
• Re: Average New Users Per DOW
  • From: Paul Jungwirth
• Re: PgBouncer error - psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.6432"?
  • From: David G. Johnston
• Average New Users Per DOW
  • From: Robert DiFalco
• Re: PgBouncer error - psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.6432"?
  • From: Igor Neyman
• Re: String match function required like utl_match in oracle
  • From: Jimit Amin
• PgBouncer error - psql: could not connect to server: No such file or directory Is the server running locally and accepting connections on Unix domain socket "/var/run/postgresql/.s.PGSQL.6432"?
  • From: Ali Aktar
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: Adrian Klaver
• Re: to_tsvector() with hyphens
  • From: Tom Lane
• to_tsvector() with hyphens
  • From: Brian DeRocher
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: Mark Morgan Lloyd
• Re: database-level lockdown
  • From: Filipe Pina
• Re: database-level lockdown
  • From: Filipe Pina
• Re: Error prone compilation of stored procedure
  • From: Pavel Stehule
• Re: Error prone compilation of stored procedure
  • From: pinker
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: Jan de Visser
• Re: unexpected data beyond EOF in block 260 of relation pg_tblspc
  • From: Adrian Klaver
• Re: Error prone compilation of stored procedure
  • From: Rob Sargent
• Re: Error prone compilation of stored procedure
  • From: Andrew Sullivan
• Re: Error prone compilation of stored procedure
  • From: pinker
• Re: Error prone compilation of stored procedure
  • From: pinker
• Re: Error prone compilation of stored procedure
  • From: Pavel Stehule
• Re: Error prone compilation of stored procedure
  • From: Andreas Kretschmer
• Error prone compilation of stored procedure
  • From: pinker
• Re: max number of locks
  • From: Fabio Pardi
• Re: dblink max per function
  • From: Peter Kroon
• next postgres version on Amazon RDS ?
  • From: Marc Mamin
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: John R Pierce
• unexpected data beyond EOF in block 260 of relation pg_tblspc
  • From: Mitu Verma
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: c.buhtz
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: Jan de Visser
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: John R Pierce
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: c.buhtz
• Fwd: dblink max per function
  • From: Peter Kroon
• Re: Why does the range type's upper function behave inconsistently?
  • From: Dane Foster
• Re: Why does the range type's upper function behave inconsistently?
  • From: Adrian Klaver
• Re: Why does the range type's upper function behave inconsistently?
  • From: Tom Lane
• Re: Why does the range type's upper function behave inconsistently?
  • From: Julien Rouhaud
• Why does the range type's upper function behave inconsistently?
  • From: Dane Foster
• Re: database-level lockdown
  • From: Greg Sabino Mullane
• Re: [pg_hba.conf] publish own Python application using PostgreSQL
  • From: Charles Clavadetscher
• [pg_hba.conf] publish own Python application using PostgreSQL
  • From: c.buhtz
• Re: trouble converting several serial queries into a parallel query
  • From: Chris Mair
• trouble converting several serial queries into a parallel query
  • From: Jonathan Vanasco
• Re: could not fork new process for connection: Resource temporarily unavailable
  • From: Joshua D. Drake
• could not fork new process for connection: Resource temporarily unavailable
  • From: Jimit Amin
• Re: database-level lockdown
  • From: Adrian Klaver
• Re: database-level lockdown
  • From: John R Pierce
• Re: database-level lockdown
  • From: Filipe Pina
• Re: return jsonb without field label
  • From: Adrian Klaver
• Re: String match function required like utl_match in oracle
  • From: Charles Clavadetscher
• String match function required like utl_match in oracle
  • From: Jimit Amin
• Re: Download PostgreSQL 9.5 Alpha
  • From: Charles Clavadetscher
• return jsonb without field label
  • From: john.tiger
• Re: Download PostgreSQL 9.5 Alpha
  • From: Joshua D. Drake
• Download PostgreSQL 9.5 Alpha
  • From: Edson F. Lidorio
• PostgreSQL & VMWare
  • From: Jean-Gérard Pailloncy
• Re: database-level lockdown
  • From: Melvin Davidson
• Re: database-level lockdown
  • From: Filipe Pina
• Re: Unusual sorting requirement (mixed enum/non-enum) - need thoughts
  • From: David G. Johnston
• Unusual sorting requirement (mixed enum/non-enum) - need thoughts
  • From: David G. Johnston
• Re: max number of locks
  • From: Adrian Klaver
• Re: Fwd: PostgreSQL & VMWare
  • From: Ibrahim Edib Kokdemir
• Re: Backup Method
  • From: Andreas Joseph Krogh
• Re: Backup Method
  • From: howardnews@xxxxxxxxxxxxx
• Re: Fwd: PostgreSQL & VMWare
  • From: Andreas Joseph Krogh
• Re: Backup Method
  • From: Bill Moran
• Re: Fwd: PostgreSQL & VMWare
  • From: Bill Moran
• Re: Backup Method
  • From: Jan Lentfer
• Re: Backup Method
  • From: howardnews@xxxxxxxxxxxxx
• Re: Backup Method
  • From: Guillaume Lelarge
• Fwd: PostgreSQL & VMWare
  • From: Jean-Gérard Pailloncy
• Re: Backup Method
  • From: howardnews@xxxxxxxxxxxxx
• Re: Backup Method
  • From: Guillaume Lelarge
• max number of locks
  • From: Fabio Pardi
• Backup Method
  • From: howardnews@xxxxxxxxxxxxx
• Re: Slow index performance
  • From: Christian Schröder
• Re: Slow index performance
  • From: Marc Mamin
• Slow index performance
  • From: Christian Schröder
• Re: very slow queries and ineffective vacuum
  • From: Pavel Stehule
• Re: very slow queries and ineffective vacuum
  • From: Sameer Kumar
• Re: Strange situation on slave server
  • From: Condor
• Re: very slow queries and ineffective vacuum
  • From: Bill Moran
• Re: Running PostgreSQL with ZFS ZIL
  • From: Joseph Kregloh
• Re: Getting the value of the old_tuple using the test_decoding extension and BDR
  • From: Sylvain MARECHAL
• Re: Running PostgreSQL with ZFS ZIL
  • From: Vick Khera
• Re: record from plpgsql function performance
  • From: Alexander Shereshevsky
• Re: very slow queries and ineffective vacuum
  • From: Melvin Davidson
• Re: Running PostgreSQL with ZFS ZIL
  • From: Joseph Kregloh
• Re: record from plpgsql function performance
  • From: David G. Johnston
• record from plpgsql function performance
  • From: Alexander Shereshevsky
• Getting the value of the old_tuple using the test_decoding extension and BDR
  • From: Sylvain MARECHAL
• Re: very slow queries and ineffective vacuum
  • From: Lukasz Wrobel
• Re: Running PostgreSQL with ZFS ZIL
  • From: Vick Khera
• Re: Ubuntu 14.04 LTS install problem
  • From: Urs Berner
• Re: Streaming Questions and Sizing
  • From: Andy Erskine
• Re: Streaming Questions and Sizing
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Andy Erskine
• Re: Streaming Questions and Sizing
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Andy Erskine
• Re: Error message in Pgpool repmgr cluster
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Andy Erskine
• Re: Ubuntu 14.04 LTS install problem
  • From: Joshua D. Drake
• Re: Ubuntu 14.04 LTS install problem
  • From: Scott Marlowe
• Re: Ubuntu 14.04 LTS install problem
  • From: Jan de Visser
• Running PostgreSQL with ZFS ZIL
  • From: Joseph Kregloh
• Error message in Pgpool repmgr cluster
  • From: shibly
• Re: Text to interval conversion can silently truncate data
  • From: Tom Lane
• Text to interval conversion can silently truncate data
  • From: Jack Christensen
• Re: Which replication is the best for our case ?
  • From: Arthur Silva
• Re: Which replication is the best for our case ?
  • From: John R Pierce
• Re: Systemd vs logging collector
  • From: Tom Lane
• Re: Systemd vs logging collector
  • From: Adrian Klaver
• Re: Systemd vs logging collector
  • From: Adrian Klaver
• Re: Ubuntu 14.04 LTS install problem
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Adrian Klaver
• Re: Streaming Questions and Sizing
  • From: Adrian Klaver
• Re: Ubuntu 14.04 LTS install problem
  • From: Urs G. Berner
• Re: Ubuntu 14.04 LTS install problem
  • From: Charles Clavadetscher
• Re: Systemd vs logging collector
  • From: Andomar
• Re: Ubuntu 14.04 LTS install problem
  • From: Jan de Visser
• Re: Ubuntu 14.04 LTS install problem
  • From: Urs Berner
• Strange situation on slave server
  • From: Condor
• Re: Which replication is the best for our case ?
  • From: ben.play
• Re: very slow queries and ineffective vacuum
  • From: Sameer Kumar
• Re: very slow queries and ineffective vacuum
  • From: Sameer Kumar
• Re: Systemd vs logging collector
  • From: Marc Mamin
• Re: how to extract the page "address" from the ctid
  • From: Marc Mamin
• Systemd vs logging collector
  • From: Andomar
• Re: Ubuntu 14.04 LTS install problem
  • From: Charles Clavadetscher
• Ubuntu 14.04 LTS install problem
  • From: Urs Berner
• Re: how to extract the page "address" from the ctid
  • From: Michael Paquier
• Streaming Questions and Sizing
  • From: Andy Erskine
• Re: very slow queries and ineffective vacuum
  • From: Melvin Davidson
• Re: very slow queries and ineffective vacuum
  • From: Alvaro Herrera
• Re: very slow queries and ineffective vacuum
  • From: William Dunn
• Re: very slow queries and ineffective vacuum
  • From: Jerry Sievers
• Re: very slow queries and ineffective vacuum
  • From: Pavel Stehule
• Re: very slow queries and ineffective vacuum
  • From: William Dunn
• Re: very slow queries and ineffective vacuum
  • From: William Dunn
• Re: very slow queries and ineffective vacuum
  • From: William Dunn
• very slow queries and ineffective vacuum
  • From: Lukasz Wrobel
• Re: Which replication is the best for our case ?
  • From: John R Pierce
• Re: Which replication is the best for our case ?
  • From: Arthur Silva
• Re: Which replication is the best for our case ?
  • From: ben.play
• Re: PgPool Configuration Document required
  • From: Joshua D. Drake
• Re: PgPool Configuration Document required
  • From: Jimit Amin
• Re: PgPool Configuration Document required
  • From: Joshua D. Drake
• Re: PgPool Configuration Document required
  • From: Melvin Davidson
• PgPool Configuration Document required
  • From: Jimit Amin
• how to extract the page "address" from the ctid
  • From: Marc Mamin
• Hardware question
  • From: Leonard Boyce
• Re: plpgsql question: select into multiple variables ?
  • From: Day, David
• Re: Feature request: fsync and commit_delay options per database
  • From: Bráulio Bhavamitra
• Re: Feature request: fsync and commit_delay options per database
  • From: Jeff Janes
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: John R Pierce
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: Michael Paquier
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: Michael Paquier
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: Tomas Vondra
• Re: Feature request: fsync and commit_delay options per database
  • From: Bráulio Bhavamitra
• Re: Feature request: fsync and commit_delay options per database
  • From: Tom Lane
• Re: serialization failure why?
  • From: Simon Riggs
• Feature request: fsync and commit_delay options per database
  • From: Bráulio Bhavamitra
• Re: plpgsql question: select into multiple variables ?
  • From: Tom Lane
• Re: plpgsql question: select into multiple variables ?
  • From: David G. Johnston
• Re: plpgsql question: select into multiple variables ?
  • From: Day, David
• Re: plpgsql question: select into multiple variables ?
  • From: Tom Lane
• Re: serialization failure why?
  • From: Kevin Grittner
• Re: plpgsql question: select into multiple variables ?
  • From: Adrian Klaver
• Re: WAL archive "resend policy"
  • From: Joshua D. Drake
• WAL archive "resend policy"
  • From: Edson Richter
• plpgsql question: select into multiple variables ?
  • From: Day, David
• Re: archive_timeout and WAL size
  • From: Edson Richter
• Re: archive_timeout and WAL size
  • From: Adrian Klaver
• archive_timeout and WAL size
  • From: Edson Richter
• Re: Which replication is the best for our case ?
  • From: John R Pierce
• Re: Which replication is the best for our case ?
  • From: Melvin Davidson
• Re: Which replication is the best for our case ?
  • From: Jeff Janes
• Re: Which replication is the best for our case ?
  • From: Arthur Silva
• Re: Which replication is the best for our case ?
  • From: Adrian Klaver
• Re: Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: Colin Lieberman
• Re: Which replication is the best for our case ?
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Which replication is the best for our case ?
  • From: Arthur Silva
• Re: Correct place for feature requests
  • From: Merlin Moncure
• Re: Need for re-index after pg_upgrade
  • From: Adrian Klaver
• Re: Need for re-index after pg_upgrade
  • From: Andreas Joseph Krogh
• Re: Need for re-index after pg_upgrade
  • From: Tom Lane
• Re: Which replication is the best for our case ?
  • From: Adrian Klaver
• Re: Which replication is the best for our case ?
  • From: Adrian Klaver
• Which replication is the best for our case ?
  • From: ben.play
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: Inserting from multiple processes?
  • From: Francisco Olarte
• Need for re-index after pg_upgrade
  • From: Andreas Joseph Krogh
• Re: pg_xlog on a hot_stanby slave
  • From: Stéphane Schildknecht
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: create index on a field of udt
  • From: Charles Clavadetscher
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: John R Pierce
• Re: Turn off streaming replication - leaving Master running
  • From: John R Pierce
• Re: Turn off streaming replication - leaving Master running
  • From: Jeff Janes
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: Michael Paquier
• Re: create index on a field of udt
  • From: Jeff Janes
• Re: create index on a field of udt
  • From: John R Pierce
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: create index on a field of udt
  • From: Shujie Shang
• Re: Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: Turn off streaming replication - leaving Master running
  • From: John R Pierce
• Re: create index on a field of udt
  • From: Charles Clavadetscher
• Re: Turn off streaming replication - leaving Master running
  • From: Michael Paquier
• Re: create index on a field of udt
  • From: John R Pierce
• Turn off streaming replication - leaving Master running
  • From: Andy Erskine
• Re: create index on a field of udt
  • From: Shujie Shang
• Re: create index on a field of udt
  • From: John R Pierce
• create index on a field of udt
  • From: Shujie Shang
• Re: Inserting from multiple processes?
  • From: Dave Johansen
• Re: Weird insert issue
  • From: Larry Meadors
• Re: Weird insert issue
  • From: Pavel Stehule
• Re: Weird insert issue
  • From: Peter Geoghegan
• Re: Weird insert issue
  • From: Pavel Stehule
• Weird insert issue
  • From: Larry Meadors
• varchar sort ordering ignore blanks - SOLVED!
  • From: Luca Arzeni
• Re: Inserting from multiple processes?
  • From: Francisco Olarte
• Re: HA
  • From: Luis Daniel Lucio Quiroz
• HA
  • From: Gerdan Rezende dos Santos
• Re: use null or 0 in foreign key column, to mean "no value"?
  • From: Alban Hertroys
• Re: use null or 0 in foreign key column, to mean "no value"?
  • From: John McKown
• Re: use null or 0 in foreign key column, to mean "no value"?
  • From: David G. Johnston
• Re: use null or 0 in foreign key column, to mean "no value"?
  • From: Jan de Visser
• Re: How to convert a text variable into a timestamp in postgreSQL?
  • From: Adrian Klaver
• use null or 0 in foreign key column, to mean "no value"?
  • From: Robert Nikander
• Re: Question about CONSTRAINT TRIGGER
  • From: David G. Johnston
• Re: How to convert a text variable into a timestamp in postgreSQL?
  • From: David G. Johnston
• Question about CONSTRAINT TRIGGER
  • From: ZM Yang
• How to convert a text variable into a timestamp in postgreSQL?
  • From: litu16
• Re: Foreign data wrappers and indexes on remote side
  • From: David G. Johnston
• Re: Foreign data wrappers and indexes on remote side
  • From: Filip Rembiałkowski
• Re: Question about the isolation level and visible
  • From: Kevin Grittner
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: litu16
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Foreign data wrappers and indexes on remote side
  • From: David G. Johnston
• Re: Foreign data wrappers and indexes on remote side
  • From: Tom Lane
• Foreign data wrappers and indexes on remote side
  • From: Filip Rembiałkowski
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: David G. Johnston
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: David G. Johnston
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: Functions, savepoints, autocommit = I am confused !
  • From: Adrian Klaver
• Re: Functions, savepoints, autocommit = I am confused !
  • From: David G. Johnston
• Functions, savepoints, autocommit = I am confused !
  • From: Tim Smith
• Re: BDR: Can a node live alone after being detached
  • From: Sylvain MARECHAL
• Re: Question about the isolation level and visible
  • From: Xiang Gan
• Re: BDR: Can a node live alone after being detached
  • From: Craig Ringer
• Question about the isolation level and visible
  • From: 娄帅
• Re: Inserting from multiple processes?
  • From: Dave Johansen
• Re: Re: INSERT a real number in a column based on other columns OLD INSERTs
  • From: Gavin Flower
• Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: Adrian Klaver
• Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: Colin Lieberman
• Re: Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: Colin Lieberman
• Get the difference between two timestamp cells but in a special format in PostgreSQL
  • From: litu16
• Re: INSERT a real number in a column based on other columns OLD INSERTs
  • From: litu16
• Re: Correct place for feature requests
  • From: Adrian Klaver
• Re: BDR: Can a node live alone after being detached
  • From: Sylvain MARECHAL
• Re: Correct place for feature requests
  • From: John R Pierce
• Re: Correct place for feature requests
  • From: Алексей Бережняк
• Re: Correct place for feature requests
  • From: David G. Johnston
• Re: Correct place for feature requests
  • From: Alvaro Herrera
• Re: Correct place for feature requests
  • From: John R Pierce
• Re: Correct place for feature requests
  • From: Tom Lane
• Re: Correct place for feature requests
  • From: Алексей Бережняк
• Re: Correct place for feature requests
  • From: Melvin Davidson
• Correct place for feature requests
  • From: Алексей Бережняк
• Re: When files in pg_multixact/{members,offsets} get recycled?
  • From: Alvaro Herrera
• When files in pg_multixact/{members,offsets} get recycled?
  • From: Piotr Gasidło
• Re: Include.d and warnings
  • From: Andomar
• Re: INSERT a real number in a column based on other columns OLD INSERTs
  • From: David G. Johnston
• Re: INSERT a real number in a column based on other columns OLD INSERTs
  • From: Adrian Klaver
• Re: Postgresql 9.2 has standby server lost data?
  • From: Paula Price
• INSERT a real number in a column based on other columns OLD INSERTs
  • From: litu16
• Pgbouncer compile in VS2013
  • From: Yelai, Ramkumar IN BLR STS
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Piotr Gackiewicz
• Re: Counting the occurences of a substring within a very large text
  • From: Albe Laurenz
• [PERFORM] pgbouncer issue
  • From: Sheena, Prabhjot
• Re: checking for NULLS in aggregate
  • From: David G. Johnston
• Re: Include.d and warnings
  • From: Adrian Klaver
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Gauthier, Dave
• checking for NULLS in aggregate
  • From: Seb
• Re: native api or odbc?
  • From: Merlin Moncure
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Francisco Olarte
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Andy Colson
• Re: Counting the occurences of a substring within a very large text
  • From: Tom Lane
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Gauthier, Dave
• Re: Counting the occurences of a substring within a very large text
  • From: Marc Mamin
• Re: mirroring a server and/or hot standby
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Include.d and warnings
  • From: Tom Lane
• Re: mirroring a server and/or hot standby
  • From: John Bleichert
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Andy Colson
• Re: DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Adrian Klaver
• Re: mirroring a server and/or hot standby
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Counting the occurences of a substring within a very large text
  • From: Geoff Winkless
• mirroring a server and/or hot standby
  • From: John Bleichert
• Re: Counting the occurences of a substring within a very large text
  • From: Marc Mamin
• DB access speeds, App(linux)<->PG(linux) vs App(linux) <->MSSql(Windows)
  • From: Gauthier, Dave
• Re: Include.d and warnings
  • From: Adrian Klaver
• Re: Counting the occurences of a substring within a very large text
  • From: Marc Mamin
• Re: Counting the occurences of a substring within a very large text
  • From: Marc Mamin
• Re: Counting the occurences of a substring within a very large text
  • From: Andy Colson
• Re: Counting the occurences of a substring within a very large text
  • From: Albe Laurenz
• Re: Counting the occurences of a substring within a very large text
  • From: Chris Mair
• Counting the occurences of a substring within a very large text
  • From: Marc Mamin
• Include.d and warnings
  • From: Andomar
• Re:
  • From: Albe Laurenz
• Re: Run analyze on schema
  • From: Suresh Raja
• Re: native api or odbc?
  • From: George Weaver
• Re: native api or odbc?
  • From: John R Pierce
• Re: native api or odbc?
  • From: Bret Stern
• native api or odbc?
  • From: Ted Toth
• Re: cascading replication and replication slots.
  • From: Andres Freund
• Re:
  • From: John R Pierce
• [no subject]
  • From: Bruno Hass de Andrade
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• cascading replication and replication slots.
  • From: Leif Gunnar Erlandsen
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Piotr Gackiewicz
• Re: cascading replication and replication_slots
  • From: Leif Gunnar Erlandsen
• Re: cascading replication and replication_slots
  • From: Michael Paquier
• cascading replication and replication_slots
  • From: Leif Gunnar Erlandsen
• Re: How to speed up pg_trgm / gin index scan
  • From: Christian Ramseyer
• Re: How to speed up pg_trgm / gin index scan
  • From: Christian Ramseyer
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: Run analyze on schema
  • From: Jerry Sievers
• Re: How to speed up pg_trgm / gin index scan
  • From: Oleg Bartunov
• Re: How to speed up pg_trgm / gin index scan
  • From: Jeff Janes
• Run analyze on schema
  • From: Suresh Raja
• Re: extracting PII data and transforming it across table.
  • From: Suresh Raja
• Re: How to speed up pg_trgm / gin index scan
  • From: Jaime Casanova
• Re: How to speed up pg_trgm / gin index scan
  • From: Christian Ramseyer
• Re: foreign keys to foreign tables
  • From: Rick Otten
• Re: foreign keys to foreign tables
  • From: Rick Otten
• Re: foreign keys to foreign tables
  • From: William Dunn
• Re: How to speed up pg_trgm / gin index scan
  • From: Jeff Janes
• Re: foreign keys to foreign tables
  • From: Tom Lane
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• foreign keys to foreign tables
  • From: Rick Otten
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: Less is More
  • From: Tom Lane
• Less is More
  • From: Paul Ramsey
• How to speed up pg_trgm / gin index scan
  • From: Christian Ramseyer
• Re: Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Albe Laurenz
• Re: Postgresql 9.2 has standby server lost data?
  • From: Albe Laurenz
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Albe Laurenz
• Re: CLOG read problem after pg_basebackup
  • From: Andres Freund
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Adrian Klaver
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: litu16
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Charles Clavadetscher
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Charles Clavadetscher
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: litu16
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Adrian Klaver
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Charles Clavadetscher
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Bill Moran
• Re: INSERT a number in a column based on other columns OLD INSERTs
  • From: Adrian Klaver
• INSERT a number in a column based on other columns OLD INSERTs
  • From: litu16
• Re: Postgresql 9.2 has standby server lost data?
  • From: Jerry Sievers
• Re: Trying to avoid a simple temporary variable declaration in a pl/pgsql function
  • From: Jerry Sievers
• Re: Trying to avoid a simple temporary variable declaration in a pl/pgsql function
  • From: Charles Clavadetscher
• Re: Trying to avoid a simple temporary variable declaration in a pl/pgsql function
  • From: David G. Johnston
• Re: Trying to avoid a simple temporary variable declaration in a pl/pgsql function
  • From: Tom Lane
• Trying to avoid a simple temporary variable declaration in a pl/pgsql function
  • From: David G. Johnston
• Re: WAL log archival on standby
  • From: Sameer Kumar
• Re: Postgresql 9.2 has standby server lost data?
  • From: Paula Price
• Re: Postgresql 9.2 has standby server lost data?
  • From: Adrian Klaver
• Re: Is there any way to measure disk activity for each query?
  • From: Julien Rouhaud
• Re: Postgres SIGALRM timer
  • From: Tom Lane
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: Postgresql 9.2 has standby server lost data?
  • From: Adrian Klaver
• Postgres SIGALRM timer
  • From: Scottix
• Postgresql 9.2 has standby server lost data?
  • From: Paula Price
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Douglas Stetner
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Piotr Gackiewicz
• Re: How to craft a query that uses memory?
  • From: Scott Marlowe
• Re: Planner cost adjustments
  • From: Daniel Begin
• Re: Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4
  • From: Adrian Klaver
• Re: How to craft a query that uses memory?
  • From: Holger.Friedrich-Fa-Trivadis
• Re: Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4
  • From: Glyn Astill
• Transaction abort difference between psql, isql, ODBC and JDBC pgsql 8.4
  • From: Gary Cowell
• Re: How to craft a query that uses memory?
  • From: Albe Laurenz
• How to craft a query that uses memory?
  • From: Holger.Friedrich-Fa-Trivadis
• Re: valgrind
  • From: Albe Laurenz
• Re: WAL log archival on standby
  • From: Michael Paquier
• WAL log archival on standby
  • From: James Sewell
• Re: Issues trying to run bdr_init_copy with new setup
  • From: Craig Ringer
• Re: Issues setting up BDR with multiple databases
  • From: Craig Ringer
• Implementing PostgreSQL in High Availability
  • From: אביאל בוסקילה
• Re: pg_xlog on a hot_stanby slave
  • From: Sameer Kumar
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Douglas Stetner
• Re: Test for char errors
  • From: Michael Paquier
• Issues setting up BDR with multiple databases
  • From: Jorge Torralba
• Re: Test for char errors
  • From: 夏高
• Re: Is there any way to measure disk activity for each query?
  • From: Jeff Janes
• Is there any way to measure disk activity for each query?
  • From: Oleg Serov
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Sheena, Prabhjot
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: ktm@xxxxxxxx
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Igor Neyman
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Jerry Sievers
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Sheena, Prabhjot
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: ktm@xxxxxxxx
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Sheena, Prabhjot
• Re: [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: ktm@xxxxxxxx
• [PERFORM] PGBOUNCER ISSUE PLEASE HELP(Slowing down the site)
  • From: Sheena, Prabhjot
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Alvaro Herrera
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• valgrind
  • From: Peter Kroon
• Re: writable cte triggers reverse order
  • From: Tom Lane
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Tom Lane
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Merlin Moncure
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Raymond O'Donnell
• Re: My postgres is not logging anymore
  • From: Raymond O'Donnell
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Chris Travers
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: Pavel Stehule
• Re: PL/pgSQL: How to return two columns and multiple rows
  • From: David G. Johnston
• PL/pgSQL: How to return two columns and multiple rows
  • From: Sven Geggus
• Re: My postgres is not logging anymore
  • From: Maila Fatticcioni
• Re: Select query regarding info
  • From: Thomas Kellerer
• Re: serialization failure why?
  • From: Simon Riggs
• Re: Select query regarding info
  • From: Bill Moran
• Re: serialization failure why?
  • From: Filipe Pina
• Re: My postgres is not logging anymore
  • From: Raymond O'Donnell
• My postgres is not logging anymore
  • From: Maila Fatticcioni
• Select query regarding info
  • From: Yogesh. Sharma
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: pg_xlog on a hot_stanby slave
  • From: Sameer Kumar
• Re: Momentary Delay
  • From: Bill Moran
• writable cte triggers reverse order
  • From: Миша Тюрин
• Re: pg_class.reltuples VS pg_stat_all_tables.n_live_tup for estimation of table
  • From: William Dunn
• Re: pg_class.reltuples VS pg_stat_all_tables.n_live_tup for estimation of table
  • From: Tom Lane
• pg_class.reltuples VS pg_stat_all_tables.n_live_tup for estimation of table
  • From: William Dunn
• Index Advice in PG
  • From: Jony Cohen
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Tom Lane
• Re: serialization failure why?
  • From: Filipe Pina
• pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Douglas Stetner
• Re: serialization failure why?
  • From: Filipe Pina
• Re: Momentary Delay
  • From: Anderson Valadares
• Re: serialization failure why?
  • From: Kevin Grittner
• Re: serialization failure why?
  • From: Filipe Pina
• Re: Test for char errors
  • From: Michael Paquier
• Test for char errors
  • From: 夏高
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Albe Laurenz
• Feature Request: bigtsvector
  • From: CPT
• Re: serialization failure why?
  • From: Bill Moran
• Re: pg_xlog on a hot_stanby slave
  • From: Sameer Kumar
• pg_dump 8.4.9 failing after upgrade to openssl-1.0.1e-30.el6_6.11.x86_64 on redhat linux
  • From: Douglas Stetner
• Re: pg_xlog on a hot_stanby slave
  • From: Venkata Balaji N
• Issues trying to run bdr_init_copy with new setup
  • From: Jorge Torralba
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: pg_xlog on a hot_stanby slave
  • From: Guillaume Lelarge
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: pg_upgrade problem
  • From: Jerry Sievers
• Re: pg_upgrade problem
  • From: Melvin Davidson
• pg_upgrade problem
  • From: Melvin Davidson
• Re: pg_xlog on a hot_stanby slave
  • From: Xavier 12
• serialization failure why?
  • From: Filipe Pina
• Re: RegisterBackgroundWorker does not actually start a bg worker process in 9.4.4
  • From: John Lumby
• Re: FW: PostgreSQL and iptables
  • From: mephysto
• Re: Compression function
  • From: Bill Moran
• Re: BDR: Can a node live alone after being detached
  • From: Craig Ringer
• Re: BDR: Can a node live alone after being detached
  • From: Sylvain MARECHAL
• Re: pg_xlog on a hot_stanby slave
  • From: Guillaume Lelarge
• pg_xlog on a hot_stanby slave
  • From: Xavier 12
• Re: Compression function
  • From: Albe Laurenz
• Compression function
  • From: "Leonardo M. Ramé"
• Re: BDR: Can a node live alone after being detached
  • From: Craig Ringer
• Re: Momentary Delay
  • From: Bill Moran
• Re: Momentary Delay
  • From: Anderson Valadares
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: localtime ?
  • From: Adrian Klaver
• Re: localtime ?
  • From: James Cloos
• Re: localtime ?
  • From: James Cloos
• Re: localtime ?
  • From: Oliver Elphick
• Re: localtime ?
  • From: Adrian Klaver
• RegisterBackgroundWorker does not actually start a bg worker process in 9.4.4
  • From: John Lumby
• Re: Row count estimation bug in BETWEEN?
  • From: Yaroslav
• Re: localtime ?
  • From: James Cloos
• Re: localtime ?
  • From: Adrian Klaver
• Re: localtime ?
  • From: James Cloos
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: pg_last_xact_replay_timestamp lies
  • From: Anton
• BDR: Can a node live alone after being detached
  • From: Sylvain MARECHAL
• Re: pg_last_xact_replay_timestamp lies
  • From: Michael Paquier
• Re: pg_last_xact_replay_timestamp lies
  • From: Anton Bushmelev
• Re: pg_last_xact_replay_timestamp lies
  • From: Michael Paquier
• pg_last_xact_replay_timestamp lies
  • From: Anton Bushmelev
• Re: Row count estimation bug in BETWEEN?
  • From: Tom Lane
• Re: Row count estimation bug in BETWEEN?
  • From: Yaroslav
• Re: Row count estimation bug in BETWEEN?
  • From: Yaroslav
• Re: Row count estimation bug in BETWEEN?
  • From: Tom Lane
• Re: FW: PostgreSQL and iptables
  • From: José María Terry Jiménez
• Row count estimation bug in BETWEEN?
  • From: Щекин Ярослав
• Re: FW: PostgreSQL and iptables
  • From: Mephysto
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Steve Kehlet
• Re: Momentary Delay
  • From: Bill Moran
• Re: [PERFORM] pg bouncer issue what does sv_used column means
  • From: ktm@xxxxxxxx
• Re: [PERFORM] pg bouncer issue what does sv_used column means
  • From: Andrew Dunstan
• Re: [PERFORM] pg bouncer issue what does sv_used column means
  • From: Sheena, Prabhjot
• Re: [PERFORM] pg bouncer issue what does sv_used column means
  • From: Xenofon Papadopoulos
• Re: pg bouncer issue what does sv_used column means
  • From: Glyn Astill
• Re: double precision[] storage space questions
  • From: greg
• log_statement = 'mod' does not log all data modifying statements
  • From: Jack Christensen
• [PERFORM] pg bouncer issue what does sv_used column means
  • From: Sheena, Prabhjot
• Re: double precision[] storage space questions
  • From: Francisco Olarte
• Re: Suggested (or existing) way to parse currency into numeric?
  • From: David G. Johnston
• Re: Suggested (or existing) way to parse currency into numeric?
  • From: Adrian Klaver
• Re: Suggested (or existing) way to parse currency into numeric?
  • From: David G. Johnston
• Re: Suggested (or existing) way to parse currency into numeric?
  • From: Adrian Klaver
• Suggested (or existing) way to parse currency into numeric?
  • From: David G. Johnston
• Re: cached row type not invalidated after DDL change
  • From: Adrian Klaver
• BDR: Node join and leave questions
  • From: sym39
• Re: database-level lockdown
  • From: Filipe Pina
• cached row type not invalidated after DDL change
  • From: Manuel Kniep
• FW: PostgreSQL and iptables
  • From: Holger.Friedrich-Fa-Trivadis
• Re: PostgreSQL and iptables
  • From: Melvin Davidson
• Re: PostgreSQL and iptables
  • From: Mephysto
• Re: PostgreSQL and iptables
  • From: Melvin Davidson
• PostgreSQL and iptables
  • From: mephysto
• Re: double precision[] storage space questions
  • From: Tom Lane
• double precision[] storage space questions
  • From: greg
• Re: user constructed where clause
  • From: Yelai, Ramkumar IN BLR STS
• Re: support for ltree
  • From: Tom Lane
• Re: Alter column from text[] to uuid[]
  • From: Keith Rarick
• Re: support for ltree
  • From: David G. Johnston
• Re: support for ltree
  • From: David G. Johnston
• Re: support for ltree
  • From: Michael Shapiro
• Re: support for ltree
  • From: Melvin Davidson
• support for ltree
  • From: Michael Shapiro
• Re: 9.3.9 ?
  • From: Magnus Hagander
• Re: 9.3.9 ?
  • From: Albe Laurenz
• 9.3.9 ?
  • From: Birta Levente
• Re: pg_bulkload
  • From: Takashi Ohnishi
• Re: localtime ?
  • From: Adrian Klaver
• Re: localtime ?
  • From: James Cloos
• Re: localtime ?
  • From: Tom Lane
• localtime ?
  • From: James Cloos
• Re: GCC error and libmpfr.so.4 not found
  • From: Asif Naeem
• Re: Alter column from text[] to uuid[]
  • From: Tom Lane
• Re: GCC error and libmpfr.so.4 not found
  • From: Asma Riyaz
• Re: Alter column from text[] to uuid[]
  • From: Adrian Klaver
• Re: GCC error and libmpfr.so.4 not found
  • From: John R Pierce
• Re: GCC error and libmpfr.so.4 not found
  • From: Asma Riyaz
• Alter column from text[] to uuid[]
  • From: Keith Rarick
• pg_bulkload
  • From: Nguyen, Phuonglan H.
• Re: GCC error and libmpfr.so.4 not found
  • From: Tom Lane
• Re: database-level lockdown
  • From: Tom Lane
• Re: GCC error and libmpfr.so.4 not found
  • From: Jimmy Yih
• database-level lockdown
  • From: Filipe Pina
• Re: GCC error and libmpfr.so.4 not found
  • From: Asma Riyaz
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Jeff Janes
• Re: GCC error and libmpfr.so.4 not found
  • From: Jimmy Yih
• Re: Random order by but first 3
  • From: David G. Johnston
• Re: SET LOCAL synchronous_commit TO OFF
  • From: Thom Brown
• Random order by but first 3
  • From: Arup Rakshit
• SET LOCAL synchronous_commit TO OFF
  • From: Robert DiFalco
• Installing Postgres manually GCC error and libmpfr.so.4 not found
  • From: asmariyaz23
• Re: Prevent roles not having admin option from granting themselves to other roles
  • From: Adrian Klaver
• Re: Prevent roles not having admin option from granting themselves to other roles
  • From: Charles Clavadetscher
• Re: GCC error and libmpfr.so.4 not found
  • From: Asma Riyaz
• Re: select count(*);
  • From: Marc Mamin
• Re: select count(*);
  • From: Geoff Winkless
• Re: select count(*);
  • From: Adrian Klaver
• Re: select count(*);
  • From: Francisco Olarte
• Re: select count(*);
  • From: Yves Dorfsman
• Re: GCC error and libmpfr.so.4 not found
  • From: Geoff Winkless
• Re: Prevent roles not having admin option from granting themselves to other roles
  • From: Charles Clavadetscher
• Re: select count(*);
  • From: Tom Lane
• Re: select count(*);
  • From: Geoff Winkless
• GCC error and libmpfr.so.4 not found
  • From: Asma Riyaz
• Re: select count(*);
  • From: Marc Mamin
• Re: select count(*);
  • From: Geoff Winkless
• Re: Planner cost adjustments
  • From: Francisco Olarte
• Re: select count(*);
  • From: Marc Mamin
• Re: select count(*);
  • From: Chris Mair
• select count(*);
  • From: Marc Mamin
• Re: Prevent roles not having admin option from granting themselves to other roles
  • From: Adrian Klaver
• Re: Planner cost adjustments
  • From: Daniel Begin
• Re: Planner cost adjustments
  • From: Bill Moran
• Prevent roles not having admin option from granting themselves to other roles
  • From: Charles Clavadetscher
• Re: Missing WALs when doing pg_basebackup from slave...
  • From: marin
• Re: Missing WALs when doing pg_basebackup from slave...
  • From: Venkata Balaji N
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Noah Misch
• Re: Planner cost adjustments
  • From: Daniel Begin
• Re: Indexed views like SQL Server - NOT Materialized Views
  • From: Kevin Grittner
• Re: Indexed views like SQL Server - NOT Materialized Views
  • From: Nicolas Paris
• Re: Indexed views like SQL Server - NOT Materialized Views
  • From: Kevin Grittner
• Missing WALs when doing pg_basebackup from slave...
  • From: marin
• Re: Indexed views like SQL Server - NOT Materialized Views
  • From: William Dunn
• Indexed views like SQL Server - NOT Materialized Views
  • From: inspector morse
• The purpose of the core team
  • From: Bruce Momjian
• Re: user constructed where clause
  • From: David G. Johnston
• user constructed where clause
  • From: Yelai, Ramkumar IN BLR STS
• Re: Postgresql BDR Replication Setup Issue
  • From: Ravi Tammineni
• Re: Inserting from multiple processes?
  • From: Dave Johansen
• Re: BDR: DDL lock problem with function inside a schema
  • From: sym39
• Re: BDR: DDL lock problem with function inside a schema
  • From: Craig Ringer
• Re: Momentary Delay
  • From: Bill Moran
• Re: Postgresql BDR Replication Setup Issue
  • From: Ian Barwick
• Re: Joins between foreign tables
  • From: Jason Dusek
• Re: Momentary Delay
  • From: Anderson Valadares
• BDR: DDL lock problem with function inside a schema
  • From: sym39
• Postgresql BDR Replication Setup Issue
  • From: Ravi Tammineni
• Re: Joins between foreign tables
  • From: Geoff Montee
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Inserting from multiple processes?
  • From: Dave Johansen
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: BDR - Failure of Primary Server - How to recover?
  • From: cchee-ob
• Re: Momentary Delay
  • From: Adrian Klaver
• Joins between foreign tables
  • From: Jason Dusek
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: Momentary Delay
  • From: Anderson Valadares
• Re: Momentary Delay
  • From: Adrian Klaver
• Momentary Delay
  • From: Anderson Valadares
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Albe Laurenz
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: David G. Johnston
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Adrian Klaver
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Adrian Klaver
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: otheus uibk
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: otheus uibk
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Tomas Vondra
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Guillaume Lelarge
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Albe Laurenz
• Re: pg_start_backup does not actually allow for consistent, file-level backup
  • From: Jan Lentfer
• pg_start_backup does not actually allow for consistent, file-level backup
  • From: otheus uibk
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: BDR - Failure of Primary Server - How to recover?
  • From: Craig Ringer
• Re: SQL Server access from PostgreSQL
  • From: Serge Fonville
• Re: SQL Server access from PostgreSQL
  • From: Geoff Montee
• Re: Thousands of schemas and ANALYZE goes out of memory
  • From: Jeff Janes
• Re: [PERFORM] Query running slow for only one specific id. (Postgres 9.3) version
  • From: Matheus de Oliveira
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Joshua D. Drake
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Tom Lane
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: alter column type
  • From: Casey Deccio
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: alter column type
  • From: John R Pierce
• Re: alter column type
  • From: Tom Lane
• Re: [PERFORM] Re: Re: Query running slow for only one specific id. (Postgres 9.3) version
  • From: Steve Crawford
• [PERFORM] Re: Re: Query running slow for only one specific id. (Postgres 9.3) version
  • From: Steve Crawford
• Re: alter column type
  • From: Ravi Krishna
• Re: alter column type
  • From: Ravi Krishna
• Re: alter column type
  • From: Casey Deccio
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Steve Kehlet
• Re: alter column type
  • From: John R Pierce
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: alter column type
  • From: Casey Deccio
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• [PERFORM] Re: Query running slow for only one specific id. (Postgres 9.3) version
  • From: Igor Neyman
• [PERFORM] Re: Query running slow for only one specific id. (Postgres 9.3) version
  • From: Sheena, Prabhjot
• Re: alter column type
  • From: Michael Nolan
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: alter column type
  • From: Ravi Krishna
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Tom Lane
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [PERFORM] Query running slow for only one specific id. (Postgres 9.3) version
  • From: Steve Crawford
• Re: alter column type
  • From: Melvin Davidson
• [PERFORM] Re: Query running slow for only one specific id. (Postgres 9.3) version
  • From: Igor Neyman
• [PERFORM] Query running slow for only one specific id. (Postgres 9.3) version
  • From: Sheena, Prabhjot
• Re: replicating many to one
  • From: Shuwn Yuan Tee
• Re: postgres_fdw - push down conditionals for ENUMs
  • From: Sergiy Zuban
• alter column type
  • From: Casey Deccio
• Re: [HACKERS] 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Tom Lane
• BDR - Failure of Primary Server - How to recover?
  • From: cchee-ob
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: Planner cost adjustments
  • From: Kevin Grittner
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Noah Misch
• Re: Database designpattern - product feature
  • From: William Dunn
• Re: replicating many to one
  • From: Sergey Konoplev
• Re: Automatic Client routing
  • From: Bill Moran
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: replicating many to one
  • From: Doiron, Daniel
• Re: replicating many to one
  • From: John R Pierce
• Re: replicating many to one
  • From: Wayne E. Seguin
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• replicating many to one
  • From: Doiron, Daniel
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: cannot connect to database through ECPG but can through psql
  • From: Tom Lane
• Re: cannot connect to database through ECPG but can through psql
  • From: Andreas Kretschmer
• cannot connect to database through ECPG but can through psql
  • From: Seann Reed
• Re: Row visibility issue with consecutive triggers, one being DEFERRED
  • From: Marc Mamin
• Re: pg_relation_size performance issue
  • From: Adrian Klaver
• Re: pg_relation_size performance issue
  • From: Melvin Davidson
• Re: pg_relation_size performance issue
  • From: Hans Guijt
• Re: pg_relation_size performance issue
  • From: Melvin Davidson
• Re: pg_relation_size performance issue
  • From: Melvin Davidson
• Re: pg_relation_size performance issue
  • From: Melvin Davidson
• Re: Row visibility issue with consecutive triggers, one being DEFERRED
  • From: Tom Lane
• Re: pg_relation_size performance issue
  • From: Tom Lane
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: Row visibility issue with consecutive triggers, one being DEFERRED
  • From: Marc Mamin
• Automatic Client routing
  • From: Ravi Krishna
• Re: pg_relation_size performance issue
  • From: Marc Mamin
• Re: pg_relation_size performance issue
  • From: Hans Guijt
• pg_relation_size performance issue
  • From: Hans Guijt
• Row visibility issue with consecutive triggers, one being DEFERRED
  • From: Marc Mamin
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Noah Misch
• Re: Database designpattern - product feature
  • From: Adrian Stern
• Re: Database designpattern - product feature
  • From: Jan de Visser
• Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: Database designpattern - product feature
  • From: Roxanne Reid-Bennett
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Andres Freund
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: Problem when temp_tablespace get full?
  • From: Jan Lentfer
• Re: Problem when temp_tablespace get full?
  • From: Daniel Begin
• Re: Database designpattern - product feature
  • From: Gmail
• Re: Problem when temp_tablespace get full?
  • From: David G. Johnston
• Problem when temp_tablespace get full?
  • From: Daniel Begin
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Robert Haas
• Re: Planner cost adjustments
  • From: Daniel Begin
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: Database designpattern - product feature
  • From: Adrian Stern
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Alvaro Herrera
• Re: Planner cost adjustments
  • From: Bill Moran
• Re: [HACKERS] Re: 9.4.1 -> 9.4.2 problem: could not access status of transaction 1
  • From: Thomas Munro
• Re: TRIGGER TRUNCATE -- CASCADE or RESTRICT
  • From: Gavin Flower
• Re: pl/python composite type array as input parameter
  • From: Adrian Klaver