Postgres Admin

• Thread Index

• Re: could not find function "LWGEOM_distance_ellipsoid_point"
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• could not find function "LWGEOM_distance_ellipsoid_point"
  • From: Stephen Davies <sdavies@xxxxxxxxxx>
• Re: What happens when PostgreSQL fails to log to SYSLOG
  • From: Craig James <cjames@xxxxxxxxxxxxxx>
• Re: What happens when PostgreSQL fails to log to SYSLOG
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: What happens when PostgreSQL fails to log to SYSLOG
  • From: "Arnold, Sandra" <ArnoldS@xxxxxxxx>
• Re: What happens when PostgreSQL fails to log to SYSLOG
  • From: "Joshua D. Drake" <jd@xxxxxxxxxxxxxxxxx>
• What happens when PostgreSQL fails to log to SYSLOG
  • From: "Arnold, Sandra" <ArnoldS@xxxxxxxx>
• Re: fail over postgres configuration
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• fail over postgres configuration
  • From: Khapare Joshi <khapare77@xxxxxxxxx>
• Re: Error: could not send data to client: Connection reset by peer
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Error: could not send data to client: Connection reset by peer
  • From: Eduardo Sá dos Reis <eduardoreis@xxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx>
• Re: Re: Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: Akash <akash.kodibail@xxxxxxxxxxxx>
• Re: auto vacuum errors
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: auto vacuum errors
  • From: Isabella Ghiurea <isabella.ghiurea@xxxxxxxxxxxxxx>
• Re: Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: auto vacuum errors
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• auto vacuum errors
  • From: Isabella Ghiurea <isabella.ghiurea@xxxxxxxxxxxxxx>
• Delay in completion of aggregation inserts when run in a single commit - PG 9.1.2
  • From: Akash Kodibail <akash.kodibail@xxxxxxxxxxxx>
• Re: webclient for postgresql
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: webclient for postgresql
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Re: webclient for postgresql
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• webclient for postgresql
  • From: "Madhu.Lanka" <mlanka@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx>
• Re: replication recovery/startup question
  • From: Greg Smith <greg@xxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Duplicate Index Creation
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Duplicate Index Creation
  • From: Samuel Stearns <SStearns@xxxxxxxxxxxxxxxx>
• Re: Oldest xmin is far in the past
  • From: Christian Rosnes <christian.rosnes@xxxxxxxxx>
• Re: Oldest xmin is far in the past
  • From: Christian Rosnes <christian.rosnes@xxxxxxxxx>
• Re: Oldest xmin is far in the past
  • From: Jerry Sievers <gsievers19@xxxxxxxxxxx>
• Oldest xmin is far in the past
  • From: Christian Rosnes <christian.rosnes@xxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: Radovan Jablonovsky <radovan.jablonovsky@xxxxxxxxxxxx>
• Re: a very slow SQL
  • From: 김준철 <dboxlist@xxxxxxxxx>
• replication recovery/startup question
  • From: Rob Cowell <Rob.Cowell@xxxxxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: Radovan Jablonovsky <radovan.jablonovsky@xxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Mike Broers <mbroers@xxxxxxxxx>
• Re: a very slow SQL
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• a very slow SQL
  • From: wangqi <wangqi@xxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Stuart Bishop <stuart@xxxxxxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: terminating autovacuum process due to administrator command
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: autovac hitting too many tables at once
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Ray Stell <stellr@xxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: starting postgres with an empty px_xlog folder
  • From: Mike Broers <mbroers@xxxxxxxxx>
• starting postgres with an empty px_xlog folder
  • From: Mike Broers <mbroers@xxxxxxxxx>
• terminating autovacuum process due to administrator command
  • From: Radovan Jablonovsky <radovan.jablonovsky@xxxxxxxxxxxx>
• Re: autovac hitting too many tables at once
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Re: autovac hitting too many tables at once
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• autovac hitting too many tables at once
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Re: about shared_buffer and kernel.shmmax
  • From: Greg Smith <greg@xxxxxxxxxxxxxxx>
• Re: about shared_buffer and kernel.shmmax
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• about shared_buffer and kernel.shmmax
  • From: wangqi <wangqi@xxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: View as front-end to function
  • From: Misa Simic <misa.simic@xxxxxxxxx>
• Re: [HACKERS] PANIC while doing failover (streaming replication)
  • From: Matheus Ricardo Espanhol <matheusespanhol@xxxxxxxxx>
• View as front-end to function
  • From: Greg Spiegelberg <gspiegelberg@xxxxxxxxx>
• Re: Issue in save and retreive file in postgres
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: "Welty, Richard" <rwelty@xxxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Simon Riggs <simon@xxxxxxxxxxxxxxx>
• Issue in save and retreive file in postgres
  • From: Vishwas Dwivedi <vishwas.sd@xxxxxxxxx>
• Re: backup
  • From: Frederiko Costa <frederiko@xxxxxxxxx>
• Re: backup
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• backup
  • From: lohita nama <namalohita@xxxxxxxxx>
• R: Re: CEST ERROR: cursor "ogrpglayerreaderxxxxxxxxx" does not exist
  • From: "francescoboccacci@xxxxxxxxx" <francescoboccacci@xxxxxxxxx>
• Re: CEST ERROR: cursor "ogrpglayerreaderxxxxxxxxx" does not exist
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• CEST ERROR: cursor "ogrpglayerreaderxxxxxxxxx" does not exist
  • From: "francescoboccacci@xxxxxxxxx" <francescoboccacci@xxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Christian Ullrich <chris@xxxxxxxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: How to install Postgresql with GSSAPI support using One click installer?
  • From: Christian Ullrich <chris@xxxxxxxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Christian Ullrich <chris@xxxxxxxxxxxxxx>
• Re: Merging two databases
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: (new thread) could not rename temporary statistics file "pg_stat_tmp/pgstat.tmp" to "pg_stat_tmp/pgstat.stat": No such file or directory
  • From: Fabricio <fabrixio1@xxxxxxxxxxx>
• Re: postgres block size alignment with filesystem block size
  • From: Bruce Momjian <bruce@xxxxxxxxxx>
• Re: Out of memory errors on pg_dump
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Out of memory errors on pg_dump
  • From: Chander Ganesan <chander.ganesan@xxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: Merging two databases
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• How to install Postgresql with GSSAPI support using One click installer?
  • From: Peter Cheung <Pcheung@xxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Peter Cheung <Pcheung@xxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Hot backup for postgres 8.4
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: Why auto vacuum almost running all the time on one toast table?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: could not rename temporary statistics file "pg_stat_tmp/pgstat.tmp" to "pg_stat_tmp/pgstat.stat": No such file or directory
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Merging two databases
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: How to setup PostgreSQL using Windows Authentication?
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Why auto vacuum almost running all the time on one toast table?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• How to setup PostgreSQL using Windows Authentication?
  • From: Peter Cheung <Pcheung@xxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• Re: Question about PITR backup
  • From: René Romero Benavides <ichbinrene@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: Creating a Read Only profile in 8.4
  • From: René Romero Benavides <ichbinrene@xxxxxxxxx>
• Re: How To Change Password Hash Algorithm From MD5 to SHA-256
  • From: Josh Kupershmidt <schmiddy@xxxxxxxxx>
• Re: Question about PITR backup
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Question about PITR backup
  • From: sgm <sgm277@xxxxxxxxxxxx>
• How To Change Password Hash Algorithm From MD5 to SHA-256
  • From: "ROMAIN, ERICKA W CTR DISA PEO-MA" <ericka.romain.ctr@xxxxxxxx>
• Re: Creating a Read Only profile in 8.4
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Creating a Read Only profile in 8.4
  • From: Jerry Sievers <gsievers19@xxxxxxxxxxx>
• Re: Creating a Read Only profile in 8.4
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Creating a Read Only profile in 8.4
  • From: "Della-Croce, Gregory" <Greg_Della-Croce@xxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• (new thread) could not rename temporary statistics file "pg_stat_tmp/pgstat.tmp" to "pg_stat_tmp/pgstat.stat": No such file or directory
  • From: Craig Ringer <ringerc@xxxxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Jerry Sievers <gsievers19@xxxxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• could not rename temporary statistics file "pg_stat_tmp/pgstat.tmp" to "pg_stat_tmp/pgstat.stat": No such file or directory
  • From: Fabricio <fabrixio1@xxxxxxxxxxx>
• pg_basebackup blocking all queries with horrible performance
  • From: Lonni J Friedman <netllama@xxxxxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: hari.fuchs@xxxxxxxxx
• Re: Hstore vs simple K:V
  • From: Richard Albright <ralbright@xxxxxxxxxxxxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Hstore vs simple K:V
  • From: A J <s5aly@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: postgres block size alignment with filesystem block size
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Postgres 9.1 Synchronous Replication and stuck queries during sync repl setup
  • From: Manoj Govindassamy <manoj@xxxxxxxxxxxxxxxxx>
• postgres block size alignment with filesystem block size
  • From: Mike Broers <mbroers@xxxxxxxxx>
• Re: Postgres 9.1 Synchronous Replication and stuck queries during sync repl setup
  • From: Gabriele Bartolini <Gabriele.Bartolini@xxxxxxxxxxxxxx>
• Postgres 9.1 Synchronous Replication and stuck queries during sync repl setup
  • From: Manoj Govindassamy <manoj@xxxxxxxxxxxxxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: hari.fuchs@xxxxxxxxx
• Re: Could the unlogged table of postgresql be used as session?
  • From: shuaixf <shuaixf@xxxxxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: Can schemas be ordered regarding their creation time ?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Can schemas be ordered regarding their creation time ?
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• How to skip StackBuilder at end of Installer?
  • From: 29t4dgru57@xxxxxxxxxxxxxx
• Re: Data split -- Creating a copy of database without outage
  • From: Jan Nielsen <jan.sture.nielsen@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: Amador Alvarez <aalvarez@xxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: Craig James <cjames@xxxxxxxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• Re: Data split -- Creating a copy of database without outage
  • From: Haifeng Liu <liuhaifeng@xxxxxxxx>
• Data split -- Creating a copy of database without outage
  • From: "Igor Shmain" <igor.shmain@xxxxxxxxx>
• Re: saved passwords lost when connection fails
  • From: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
• Re: saved passwords lost when connection fails
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• saved passwords lost when connection fails
  • From: Michael Shapiro <mshapiro51@xxxxxxxxx>
• PG_DUMP producing lots of WAL archive logs
  • From: Adam Fuchs <atman@xxxxxxx>
• Re: introduction
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• introduction
  • From: matthias <Matthias@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: out of memory error
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• out of memory error
  • From: Vincent Dautremont <vincent@xxxxxxxxxxxxxxxx>
• Re: dangling connections
  • From: Daryl Stultz <daryl.stultz@xxxxxxxxxxxxx>
• Problem with SSL certificate setup; please disregard -- solution found.
  • From: Robert Bruccoleri <bruc@xxxxxxxxxxxxxxxxxxxxx>
• Problem with SSL certificate setup
  • From: Robert Bruccoleri <bruc@xxxxxxxxxxxxxxxxxxxxx>
• Re: Transaction ID overrun problem on greenplum
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Transaction ID overrun problem on greenplum
  • From: "Little, Douglas" <DOUGLAS.LITTLE@xxxxxxxxxx>
• Re: Run external program from postgresql
  • From: Fabrízio de Royes Mello <fabriziomello@xxxxxxxxx>
• Re: Run external program from postgresql
  • From: Fabrízio de Royes Mello <fabriziomello@xxxxxxxxx>
• R: Re: Run external program from postgresql
  • From: "francescoboccacci@xxxxxxxxx" <francescoboccacci@xxxxxxxxx>
• Re: Run external program from postgresql
  • From: Fabrízio de Royes Mello <fabriziomello@xxxxxxxxx>
• Run external program from postgresql
  • From: "francescoboccacci@xxxxxxxxx" <francescoboccacci@xxxxxxxxx>
• Re: What does a .1 suffix on a PG data file signify?
  • From: "ktm@xxxxxxxx" <ktm@xxxxxxxx>
• What does a .1 suffix on a PG data file signify?
  • From: David Schnur <dnschnur@xxxxxxxxx>
• Re: dangling connections
  • From: Daryl Stultz <daryl.stultz@xxxxxxxxxxxxx>
• Re: dangling connections
  • From: Daryl Stultz <daryl.stultz@xxxxxxxxxxxxx>
• Re: dangling connections
  • From: Sergey Konoplev <gray.ru@xxxxxxxxx>
• Monitoring for failed autovacuum
  • From: John Rouillard <rouilj@xxxxxxxxxxx>
• Re: CPU Load question / PgBouncer config
  • From: "ktm@xxxxxxxx" <ktm@xxxxxxxx>
• CPU Load question / PgBouncer config
  • From: "Benjamin Krajmalnik" <kraj@xxxxxxxxxxxxx>
• dangling connections
  • From: Daryl Stultz <daryl.stultz@xxxxxxxxxxxxx>
• FW: pg_dump: schema with OID 2200 does not exist
  • From: Elizandro Gallegos <elizandro_gv@xxxxxxxxxxx>
• Re: [SQL] pg_dump: aborting because of server version mismatch
  • From: Adrian Klaver <adrian.klaver@xxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: Bruce Momjian <bruce@xxxxxxxxxx>
• PG 9.1 wal archiving
  • From: Kasia Tuszynska <ktuszynska@xxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: Extension prevents dumping table?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Extension prevents dumping table?
  • From: Chander Ganesan <chander.ganesan@xxxxxxxxx>
• Re: FW: pg_dump: schema with OID 2200 does not exist
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• FW: pg_dump: schema with OID 2200 does not exist
  • From: Elizandro Gallegos <elizandro_gv@xxxxxxxxxxx>
• Re: pg_dump: schema with OID 2200 does not exist
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• pg_dump: schema with OID 2200 does not exist
  • From: Chander Ganesan <chander.ganesan@xxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: increasing max_pred_locks_per_transaction, what shuold I look for?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• increasing max_pred_locks_per_transaction, what shuold I look for?
  • From: Brian Ferhle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: retaining useful information on my screen
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: retaining useful information on my screen
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: retaining useful information on my screen
  • From: "Tim Bruce - Postgres" <postgres@xxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• retaining useful information on my screen
  • From: "Fred Parkinson" <FredP@xxxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: Advice/guideline on increasing shared_buffers and kernel parameters
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Advice/guideline on increasing shared_buffers and kernel parameters
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: Thomas Markus <t.markus@xxxxxxxxxxxxx>
• Re: SQLSTATE 53100 could not extend file / disk full
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• SQLSTATE 53100 could not extend file / disk full
  • From: "Jan-Peter Seifert" <Jan-Peter.Seifert@xxxxxx>
• C/C++ Linker Problem in Postgres extension functions
  • From: Craig James <cjames@xxxxxxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "ktm@xxxxxxxx" <ktm@xxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Getting "ident" to work in Windows
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "ktm@xxxxxxxx" <ktm@xxxxxxxx>
• Re: Getting "ident" to work in Windows
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Re: Getting "ident" to work in Windows
  • From: "ktm@xxxxxxxx" <ktm@xxxxxxxx>
• Re: Getting "ident" to work in Windows
  • From: Magnus Hagander <magnus@xxxxxxxxxxxx>
• Getting "ident" to work in Windows
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: postgresql stream replication question
  • From: sgm <sgm277@xxxxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: DELETE and UPDATE triggers on parent table of partioned table not firing.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• DELETE and UPDATE triggers on parent table of partioned table not firing.
  • From: "Plugge, Joe R." <JRPlugge@xxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Very long "<IDLE> in transaction" query
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Very long "<IDLE> in transaction" query
  • From: "Gnanakumar" <gnanam@xxxxxxxxxx>
• Re: postgresql stream replication question
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• postgresql stream replication question
  • From: sgm <sgm277@xxxxxxxxxxxx>
• Re: [seapug] Re: [BUGS] pg_dump: aborting because of server version mismatchT
  • From: Robert Bernier <rbernier@xxxxxxxxxxxxxxxx>
• pg_dump: aborting because of server version mismatch
  • From: Mitesh Shah <mitesh.shah@xxxxxxxxxxxxx>
• Re: [BUGS] pg_dump: aborting because of server version mismatch
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: grant select pg 9.0.3
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• grant select pg 9.0.3
  • From: Tony Capobianco <tcapobianco@xxxxxxxxxxxxxx>
• Re: unexpected EOF on client connection / could not send data to client: Broken pipe
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• unexpected EOF on client connection / could not send data to client: Broken pipe
  • From: Hariraman Jayaraj <hariraman.ocp@xxxxxxxxx>
• Re: Any public dataset for benchmarking?
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: Any public dataset for benchmarking?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Any public dataset for benchmarking?
  • From: Bèrto ëd Sèra <berto.d.sera@xxxxxxxxx>
• Re: database system identifier differs between the primary and standby
  • From: DM <dm.aeqa@xxxxxxxxx>
• Re: Postgres shared memory error
  • From: Fernando Hevia <fhevia@xxxxxxxxx>
• Re: Configuring pg on os x lion
  • From: Andrew Barinov <andy.lauerbarinov@xxxxxx>
• Re: Configuring pg on os x lion
  • From: Andrew Barinov <andy.lauerbarinov@xxxxxx>
• Re: Postgres shared memory error
  • From: Kevin Kempter <cs_dba@xxxxxxxxxxxxxxxxxxx>
• Re: Postgres shared memory error
  • From: Fernando Hevia <fhevia@xxxxxxxxx>
• Postgres shared memory error
  • From: Kevin Kempter <cs_dba@xxxxxxxxxxxxxxxxxxx>
• Re: Configuring pg on os x lion
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Re: psql: could not connect to server: No route to host
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Configuring pg on os x lion
  • From: Andrew Barinov <andy.lauerbarinov@xxxxxx>
• Re: psql: could not connect to server: No route to host
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: psql: could not connect to server: No route to host
  • From: Kevin Kempter <cs_dba@xxxxxxxxxxxxxxxxxxx>
• Fwd: psql: could not connect to server: No route to host
  • From: Ricardo Benatti <rbenatti@xxxxxxxxx>
• Re: psql: could not connect to server: No route to host
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: psql: could not connect to server: No route to host
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• psql: could not connect to server: No route to host
  • From: Kevin Kempter <cs_dba@xxxxxxxxxxxxxxxxxxx>
• Re: Query REST Service
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Query REST Service
  • From: Ricardo Bayley <ricardo.bayley@xxxxxxxxx>
• Re: Backup/disaster recovery and bandwidth (long)
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: Backup/disaster recovery and bandwidth (long)
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Re: Backup/disaster recovery and bandwidth (long)
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Backup/disaster recovery and bandwidth (long)
  • From: Scott Whitney <scott@xxxxxxxxxxx>
• Re: Backup/disaster recovery and bandwidth (long)
  • From: amador alvarez <aalvarez@xxxxxx>
• Backup/disaster recovery and bandwidth (long)
  • From: Scott Whitney <scott@xxxxxxxxxxx>
• Making PostgreSQL portable on WinXP
  • From: BGoebel <b.goebel@xxxxxxxxxxxxxxxxxx>
• Re: pg_dump: schema with OID 145167 does not exist
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: Calling a plpgsql function with an array of results?
  • From: Naoko Reeves <naokoreeves@xxxxxxxxx>
• Calling a plpgsql function with an array of results?
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Partial substrings in FTS
  • From: Jesper Krogh <jesper@xxxxxxxx>
• Re: Partial substrings in FTS
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Partial substrings in FTS
  • From: A J <s5aly@xxxxxxxxx>
• Re: Getting that starts a week of the year
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Getting that starts a week of the year
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: What is the role of pg_filenode.map ?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• What is the role of pg_filenode.map ?
  • From: "F. BROUARD / SQLpro" <sqlpro@xxxxxxxxxxxxxxxx>
• Getting that starts a week of the year
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Unending DB migration
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: Unending DB migration
  • From: Walter Hurry <walterhurry@xxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• Re: ERROR: invalid input syntax for type timestamp: ""
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: How to auto swtich the roles of primary and standby
  • From: videanuadrian <videanuadrian@xxxxxxxxx>
• Re: Urgent help required
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: UNIX vs Windows LC CTYPE and UPPER mu
  • From: Peter Eisentraut <peter_e@xxxxxxx>
• Re: Urgent help required
  • From: Scott Mead <scottm@xxxxxxxxxxx>
• Urgent help required
  • From: Nagaraj Shindagi <nagaraj.shindagi@xxxxxxxxx>
• Re: Unending DB migration
  • From: Peter Steinheuser <psteinheuser@xxxxxxxxxxxxxx>
• Re: Unending DB migration
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Unending DB migration
  • From: ЇЯЅHAÐ <irshad.nazir@xxxxxxxxx>
• Re: How to auto swtich the roles of primary and standby
  • From: jenopob <jenopob@xxxxxxx>
• ERROR: invalid input syntax for type timestamp: ""
  • From: "Kshirsagar, Swanand" <Swanand.Kshirsagar@xxxxxxxxxxx>
• Re: How to auto swtich the roles of primary and standby
  • From: videanuadrian <videanuadrian@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Clarification on start/stop backup
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: UNIX vs Windows LC CTYPE and UPPER mu
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Cannot Connect To Db From Local Server
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Cannot Connect To Db From Local Server
  • From: "Rickard, David" <drickard1967@xxxxxxxxxxxxxxxx>
• Re: Cannot Connect To Db From Local Server
  • From: Scott Mead <scottm@xxxxxxxxxxx>
• Clarification on start/stop backup
  • From: Scott Whitney <scott@xxxxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• UNIX vs Windows LC CTYPE and UPPER mu
  • From: service prodat <service@xxxxxxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Chris Ernst <cernst@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Igor Neyman <ineyman@xxxxxxxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: How to auto swtich the roles of primary and standby
  • From: videanuadrian <videanuadrian@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Chris Ernst <cernst@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Chris Ernst <cernst@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Chris Ernst <cernst@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• enterprisedb package and pam on debian
  • From: Uwe Bartels <uwe.bartels@xxxxxxxxx>
• Re: Recreate primary key without dropping foreign keys?
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Recreate primary key without dropping foreign keys?
  • From: Chris Ernst <cernst@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Trouble w/ COPY command
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Trouble w/ COPY command
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Trouble w/ COPY command
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• invalid byte sequence for encoding "UTF8": 0xf481 - how could this happen?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Changing max_connections after WAL slave configured not allowed?
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Changing max_connections after WAL slave configured not allowed?
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Definitive logrotate solution?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Definitive logrotate solution?
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Definitive logrotate solution?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Definitive logrotate solution?
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Recovery mode for a WAL-based slave
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Recovery mode for a WAL-based slave
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: "L'Huillier, Jeff" <Jeff.LHuillier@xxxxxxxxxx>
• Re: 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: "L'Huillier, Jeff" <Jeff.LHuillier@xxxxxxxxxx>
• Re: 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• 9.0.4/7 WAL Archiving: archive_command add date-time to cp of filename
  • From: "L'Huillier, Jeff" <Jeff.LHuillier@xxxxxxxxxx>
• Re: Warnings in Standby Logs
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: Writing to a database or schema on a slave
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Writing to a database or schema on a slave
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Writing to a database or schema on a slave
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Writing to a database or schema on a slave
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Setting up streaming replication w/ a big ole database
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Setting up streaming replication w/ a big ole database
  • From: Robert Burgholzer <rburghol@xxxxxx>
• Re: Setting up streaming replication w/ a big ole database
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Setting up streaming replication w/ a big ole database
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Setting up streaming replication w/ a big ole database
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Setting up streaming replication w/ a big ole database
  • From: Wells Oliver <wellsoliver@xxxxxxxxx>
• Re: Why would queries fail with 'could not stat file' after CLUSTER?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: "Albe Laurenz" <laurenz.albe@xxxxxxxxxx>
• Re: Giant Postgresql Database Cluster Folder
  • From: robin <robin@xxxxxxxxxx>
• Re: Why would queries fail with 'could not stat file' after CLUSTER?
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Re: Giant Postgresql Database Cluster Folder
  • From: raghu ram <raghuchennuru@xxxxxxxxx>
• Giant Postgresql Database Cluster Folder
  • From: Kiruba suthan <kirubasuthan@xxxxxxxxx>
• Re: Why would queries fail with 'could not stat file' after CLUSTER?
  • From: Sashbeer Bhandari <sashbeer@xxxxxxxxx>
• Re: Why would queries fail with 'could not stat file' after CLUSTER?
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Why would queries fail with 'could not stat file' after CLUSTER?
  • From: David Schnur <dnschnur@xxxxxxxxx>
• Re: libpqxx for x86 builds of RHEL?
  • From: Dave Johansen <davejohansen@xxxxxxxxx>
• Re: libpqxx for x86 builds of RHEL?
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Re: libpqxx for x86 builds of RHEL?
  • From: Dave Johansen <davejohansen@xxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Matt Williams <matt@xxxxxxxxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Matt Williams <matt@xxxxxxxxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Matt Williams <matt@xxxxxxxxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Scott Whitney <scott@xxxxxxxxxxx>
• Re: utf8 database not dumping utf8 characters
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• utf8 database not dumping utf8 characters
  • From: Matt Williams <matt@xxxxxxxxxxxxxxxxx>
• Re: replication failure with GIN index
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: libpqxx for x86 builds of RHEL?
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Re: replication failure with GIN index
  • From: Simon Riggs <simon@xxxxxxxxxxxxxxx>
• replication failure with GIN index
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• libpqxx for x86 builds of RHEL?
  • From: Dave Johansen <davejohansen@xxxxxxxxx>
• Re: check_postgresql.pl for zabbix
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: about multiprocessingmassdata
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: check_postgresql.pl for zabbix
  • From: Bèrto ëd Sèra <berto.d.sera@xxxxxxxxx>
• alter index's tablespace (from default) after pg_upgrade --link
  • From: MirrorX <mirrorx@xxxxxxxxx>
• Re: check_postgresql.pl for zabbix
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• check_postgresql.pl for zabbix
  • From: Bèrto ëd Sèra <berto.d.sera@xxxxxxxxx>
• about multiprocessingmassdata
  • From: superman0920 <superman0920@xxxxxxxxx>
• Segmentation fault ( after Shared Lock acquired, same table 4 times )
  • From: Jan Mussler <janm81@xxxxxxxxxxxxxx>
• Re: custom conflict resolution information request
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: custom conflict resolution information request
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Warnings in Standby Logs
  • From: masterchief <esimon@xxxxxxxxxxxxxx>
• Re: about encoding
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Segmentation fault ( after Shared Lock acquired, same table 4 times )
  • From: Jan Mussler <janm81@xxxxxxxxxxxxxx>
• Re: PGadmin PostgresSQL
  • From: Scott Whitney <swhitney@xxxxxxxxxxx>
• Re: Warnings in Standby Logs
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: PGadmin PostgresSQL
  • From: Dick Visser <visser@xxxxxxxxxx>
• about encoding
  • From: superman0920 <superman0920@xxxxxxxxx>
• PGadmin PostgresSQL
  • From: "Tim Dons" <t.dons@xxxxxxxxxx>
• Postgres Zip init not creating db user windows
  • From: sagarika rao <sagari.rao@xxxxxxxxx>
• Windows client only psql install
  • From: Laura Moloney <LMoloney@xxxxxxxxxxxx>
• Warnings in Standby Logs
  • From: "Eric Simon" <esimon@xxxxxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Vladimir Rusinov <vladimir@xxxxxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Bernhard Schrader <bernhard.schrader@xxxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• custom conflict resolution information request
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: about encoding
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Bernhard Schrader <bernhard.schrader@xxxxxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• Re: pg_database_size() and actual disk space usage
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• pg_database_size() and actual disk space usage
  • From: Alexander Fortin <alexander.fortin@xxxxxxxxx>
• about encoding
  • From: superman0920 <superman0920@xxxxxxxxx>
• Re: Daily Rotated Insertion
  • From: Haifeng Liu <liuhaifeng@xxxxxxxx>
• Re: Daily Rotated Insertion
  • From: Sergey Konoplev <gray.ru@xxxxxxxxx>
• Re: Daily Rotated Insertion
  • From: Haifeng Liu <liuhaifeng@xxxxxxxx>
• Re: Daily Rotated Insertion
  • From: Sergey Konoplev <gray.ru@xxxxxxxxx>
• Daily Rotated Insertion
  • From: Haifeng Liu <liuhaifeng@xxxxxxxx>
• Re: german sort is wrong
  • From: BGoebel <b.goebel@xxxxxxxxxxxxxxxxxx>
• Re: WAL archiving question
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• WAL archiving question
  • From: Debanjan Bhattacharyya <b.debanjan@xxxxxxxxx>
• pg_dump: schema with OID 145167 does not exist
  • From: "Paul Wouters" <paul.wouters@xxxxxxxxxxx>
• Re: german sort is wrong
  • From: Reinhard Asmus <reinhard.asmus@xxxxxxxxxxxxxx>
• Re: New role can connect to all dbs with no grants
  • From: Gordon Shannon <gordo169@xxxxxxxxx>
• Re: deciding between amd and intel processor
  • From: Imre Oolberg <imre@xxxxxxxxxxx>
• Re: postgresql91-devel no include [pg_config] ??
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Re: pg_dump: schema with OID 145167 does not exist
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: german sort is wrong
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• pg_dump: schema with OID 145167 does not exist
  • From: "Paul Wouters" <paul.wouters@xxxxxxxxxxx>
• Re: german sort is wrong
  • From: Reinhard Asmus <reinhard.asmus@xxxxxxxxxxxxxx>
• Re: german sort is wrong
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• german sort is wrong
  • From: Reinhard Asmus <reinhard.asmus@xxxxxxxxxxxxxx>
• Re: deciding between amd and intel processor
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: deciding between amd and intel processor
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• deciding between amd and intel processor
  • From: Imre Oolberg <imre@xxxxxxxxxxx>
• Re: New role can connect to all dbs with no grants
  • From: Mark Lane <dartflight@xxxxxxxxx>
• New role can connect to all dbs with no grants
  • From: Gordon Shannon <gordo169@xxxxxxxxx>
• Re: clustering with shared storage
  • From: Rosser Schwarz <rosser.schwarz@xxxxxxxxx>
• Re: clustering with shared storage
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Re: clustering with shared storage
  • From: amador alvarez <aalvarez@xxxxxx>
• Re: clustering with shared storage
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• clustering with shared storage
  • From: Gary Webster <webster@xxxxxxxxxxx>
• Warnings in Standby Logs
  • From: masterchief <esimon@xxxxxxxxxxxxxx>
• Re: ALTER ROLE foo SET log_connections = true;
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: ALTER ROLE foo SET log_connections = true;
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• ALTER ROLE foo SET log_connections = true;
  • From: "Marc Mamin" <M.Mamin@xxxxxxxxxxxx>
• Re: Enabling Windows Authentication
  • From: Christian Ullrich <chris@xxxxxxxxxxxxxx>
• Re: Streaming Replication Hooks
  • From: Sergey Konoplev <gray.ru@xxxxxxxxx>
• Streaming Replication Hooks
  • From: David Fennell <david.fennell@xxxxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Walter Hurry <walterhurry@xxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Robin Iddon <robin@xxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Kris Deugau <kdeugau@xxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: David Ondrejik <david.ondrejik@xxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: David Ondrejik <david.ondrejik@xxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: David Ondrejik <david.ondrejik@xxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Robin Iddon <robin@xxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• Re: Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Robin Iddon <robin@xxxxxxxxxx>
• Update actions (with user name) inside PostgreSQL DB - any version on postgreSQL
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• postgresql91-devel no include [pg_config] ??
  • From: Gabriel Pinares <glupiado@xxxxxxxxx>
• Re: archive_command and streaming replication
  • From: MirrorX <mirrorx@xxxxxxxxx>
• Re: triggers are not shared between parent and child tables?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: triggers are not shared between parent and child tables?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: triggers are not shared between parent and child tables?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: How to back up selected rows using
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• How to back up selected rows using
  • From: Piyush Lenka <lenka.piyush@xxxxxxxxx>
• Re: triggers are not shared between parent and child tables?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• triggers are not shared between parent and child tables?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Looking for help on backing up a large database (500GB+) with LOBs
  • From: David Kerr <dmk@xxxxxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Achilleas Mantzios <achill@xxxxxxxxxxxxxxxxxxx>
• archive_command and streaming replication
  • From: Martin von Oertzen <maletin@xxxxxxxx>
• Looking for help on backing up a large database (500GB+) with LOBs
  • From: Todd Hunt <Todd.Hunt@xxxxxxxxx>
• Enabling Windows Authentication
  • From: Noel Simela <nsimela@xxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: c k <shreeseva.learning@xxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Re: Disable TRUST authentication mode
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: c k <shreeseva.learning@xxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Re: Disable TRUST authentication mode
  • From: c k <shreeseva.learning@xxxxxxxxx>
• Re: Disable TRUST authentication mode
  • From: Jan Lentfer <Jan.Lentfer@xxxxxx>
• Disable TRUST authentication mode
  • From: c k <shreeseva.learning@xxxxxxxxx>
• Re: postgresql monitoring tool (GUI)
  • From: Filippos <filippos.kal@xxxxxxxxx>
• Re: postgresql monitoring tool (GUI)
  • From: Rick Dicaire <kritek@xxxxxxxxx>
• postgresql monitoring tool (GUI)
  • From: Filippos <filippos.kal@xxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: "umashankar narayanan" <umashankar@xxxxxxxxxxxx>
• Re: Vacuum to prevent wraparound data loss
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Vacuum to prevent wraparound data loss
  • From: Natalie Wenz <nataliewenz@xxxxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: "umashankar narayanan" <umashankar@xxxxxxxxxxxx>
• Postgres 8.3 crashing unexpectedly
  • From: "umashankar narayanan" <umashankar@xxxxxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Postgres server crashing unexpectedly.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: table names seem identical
  • From: David Kerr <dmk@xxxxxxxxxxxxxx>
• Postgres server crashing unexpectedly.
  • From: "umashankar narayanan" <umashankar@xxxxxxxxxxxx>
• Re: logging issue
  • From: "Campbell, Lance" <lance@xxxxxxxxxxxx>
• Re: table names seem identical
  • From: Ray Stell <stellr@xxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: table names seem identical
  • From: Walter Hurry <walterhurry@xxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: speedup pg_dumpall
  • From: Michael Monnerie <lists.michael.monnerie@xxxxxxxxxxxxxxxxxxx>
• table names seem identical
  • From: Ray Stell <stellr@xxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: pg_attribute file in PostgreSQL 9.0
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• pg_attribute file in PostgreSQL 9.0
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: I've got gaps in the log files?
  • From: "Greg Sabino Mullane" <greg@xxxxxxxxxxxx>
• Re: I've got gaps in the log files?
  • From: Andreas <maps.on@xxxxxxx>
• Re: logging issue
  • From: Jerry Sievers <gsievers19@xxxxxxxxxxx>
• logging issue
  • From: "Campbell, Lance" <lance@xxxxxxxxxxxx>
• Re: I've got gaps in the log files?
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• I've got gaps in the log files?
  • From: Andreas <maps.on@xxxxxxx>
• Re: pg_dump : no tables were found.
  • From: Julien Rouhaud <rjuju123@xxxxxxxxx>
• pg_dump : no tables were found.
  • From: Piyush Lenka <lenka.piyush@xxxxxxxxx>
• Re: Restoring selected records from backup file
  • From: davidh <david@xxxxxxxxxxxxx>
• Re: Safe to put indexes in tablespaces on raid0 disk?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: Safe to put indexes in tablespaces on raid0 disk?
  • From: "Nicholson, Brad (Toronto, ON, CA)" <bnicholson@xxxxxx>
• Safe to put indexes in tablespaces on raid0 disk?
  • From: Rural Hunter <ruralhunter@xxxxxxxxx>
• Re: re-create information_schema
  • From: Ray Stell <stellr@xxxxxxxxxx>
• Re: re-create information_schema
  • From: Peter Eisentraut <peter_e@xxxxxxx>
• Restoring selected records from backup file
  • From: Piyush Lenka <lenka.piyush@xxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: Can't recover data from a .tar.gz file which was backed up using COPY BINARY command
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• Re: Can't recover data from a .tar.gz file which was backed up using COPY BINARY command
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Simon Riggs <simon@xxxxxxxxxxxxxxx>
• Can't recover data from a .tar.gz file which was backed up using COPY BINARY command
  • From: Khangelani Gama <kgama@xxxxxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Re: re-create information_schema
  • From: Ray Stell <stellr@xxxxxxxxxx>
• re-create information_schema
  • From: Ray Stell <stellr@xxxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: Failover of a Hot standby setup with multiple standbys
  • From: Sergey Konoplev <gray.ru@xxxxxxxxx>
• Re: Hot standby having high requested checkpoints?
  • From: Fujii Masao <masao.fujii@xxxxxxxxx>
• Hot standby having high requested checkpoints?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: Monitor without superuser?
  • From: Greg Smith <greg@xxxxxxxxxxxxxxx>
• Failover of a Hot standby setup with multiple standbys
  • From: Deepesh D <deep.d2010@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Lennin Caro <lennin.caro@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Lennin Caro <lennin.caro@xxxxxxxxx>
• Large amount of postgres processes
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Brian Weaver <cmdrclueless@xxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Brian Weaver <cmdrclueless@xxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Brian Weaver <cmdrclueless@xxxxxxxxx>
• Re: Problems with pg_restore (plpgsql already exists)
  • From: Dinesh Bhandary <dbhandary@xxxxxxx>
• Problems with pg_restore (plpgsql already exists)
  • From: Brian Weaver <cmdrclueless@xxxxxxxxx>
• Re: logfile per DataBase
  • From: "Igor Neyman" <ineyman@xxxxxxxxxxxxxx>
• logfile per DataBase
  • From: Lutz Steinborn <l.steinborn@xxxxxxxx>
• Re: Can't query the sequence table of a serial primary key.
  • From: "Fred Parkinson" <FredP@xxxxxxxxxxx>
• Re: Can't query the sequence table of a serial primary key.
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Can't query the sequence table of a serial primary key.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Can't query the sequence table of a serial primary key.
  • From: "Fred Parkinson" <FredP@xxxxxxxxxxx>
• Re: speedup pg_dumpall
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: WAL files containing old and unmodified data?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: Vacuuming
  • From: Rick Dicaire <kritek@xxxxxxxxx>
• Vacuuming
  • From: Philip Edelbrock <phil@xxxxxxxxxxxxxxxxxx>
• Re: WAL files containing old and unmodified data?
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• WAL files containing old and unmodified data?
  • From: Brian Fehrle <brianf@xxxxxxxxxxxxxxxxxxx>
• Re: constraints primary key and foreign key lost.
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• constraints primary key and foreign key lost.
  • From: Gera Mel Handumon <geramel.h@xxxxxxxxx>
• speedup pg_dumpall
  • From: Michael Monnerie <lists.michael.monnerie@xxxxxxxxxxxxxxxxxxx>
• Re: R: Out of memory...
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• R: Out of memory...
  • From: "Cassiano, Marco" <mcassiano@xxxxxxxxxx>
• sql query variables not expanded in log file
  • From: Rick Dicaire <kritek@xxxxxxxxx>
• Re: Connections to the Database
  • From: Raghavendra <raghavendra.rao@xxxxxxxxxxxxxxxx>
• Re: Connections to the Database
  • From: Reinhard Asmus <reinhard.asmus@xxxxxxxxxxxxxx>
• Re: Out of memory...
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Big difference in databasesize compared with disksize
  • From: Steve Crawford <scrawford@xxxxxxxxxxxxxxxxxxxx>
• Out of memory...
  • From: "Cassiano, Marco" <mcassiano@xxxxxxxxxx>
• Monitor without superuser?
  • From: Jan Nielsen <jan.sture.nielsen@xxxxxxxxx>
• Re: Connections to the Database
  • From: lst_hoe02@xxxxxxxxx
• mailing CSV results
  • From: Dick Visser <visser@xxxxxxxxxx>
• Re: Big difference in databasesize compared with disksize
  • From: Bernhard Schrader <bernhard.schrader@xxxxxxxxxxxx>
• Re: Connections to the Database
  • From: Adarsh Sharma <adarsh.sharma@xxxxxxxxxx>
• Connections to the Database
  • From: Reinhard Asmus <reinhard.asmus@xxxxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Khusro Jaleel <mailing-lists@xxxxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Ian Lea <ian.lea@xxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Khusro Jaleel <mailing-lists@xxxxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Khusro Jaleel <mailing-lists@xxxxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Khusro Jaleel <mailing-lists@xxxxxxxxxxxxxx>
• Re: Backing up a replication set every 30 mins
  • From: Vladimir Rusinov <vladimir@xxxxxxxxxxxxxx>
• Backing up a replication set every 30 mins
  • From: Khusro Jaleel <mailing-lists@xxxxxxxxxxxxxx>
• Error in log
  • From: Frank Lanitz <frank@xxxxxxxxxxxxxx>
• Re: Real time monitoring of pg_dump progress through web apps
  • From: Anup Greens <agreens123@xxxxxxxxx>
• Re: Real time monitoring of pg_dump progress through web apps
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Big difference in databasesize compared with disksize
  • From: Bernhard Schrader <bernhard.schrader@xxxxxxxxxxxx>
• Real time monitoring of pg_dump progress through web apps
  • From: Anup Greens <agreens123@xxxxxxxxx>
• Re: postgres backup ( logical using pg_dump) using AMANDA
  • From: Walter Hurry <walterhurry@xxxxxxxxxxx>
• Re: postgres backup ( logical using pg_dump) using AMANDA
  • From: Dinesh Bhandary <dbhandary@xxxxxxx>
• Re: postgres backup ( logical using pg_dump) using AMANDA
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• postgres backup ( logical using pg_dump) using AMANDA
  • From: Dinesh Bhandary <dbhandary@xxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: Devrim GÜNDÜZ <devrim@xxxxxxxxxx>
• Re: Automatic Failover Hot Standby / Streaming replication
  • From: 杨晓青 <xqy1522@xxxxxxxxx>
• Automatic Failover Hot Standby / Streaming replication
  • From: Wissem <kiwan2005@xxxxxxxxx>
• Re: User password encryption using a stronger hashing function?
  • From: Bruce Momjian <bruce@xxxxxxxxxx>
• Re: 32-bit to 64-bit migration options
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxxxxxxxxxxxxxxx>
• Re: 32-bit to 64-bit migration options
  • From: Guillaume Lelarge <guillaume@xxxxxxxxxxxx>
• 32-bit to 64-bit migration options
  • From: Greg Spiegelberg <gspiegelberg@xxxxxxxxxxxxx>
• Segmentation fault/compressed data is corrupted.
  • From: Lukasz Brodziak <lukasz.brodziak@xxxxxxxxxxxxx>
• Re: postgres 9.0 date aberration in logs
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Re: postgres 9.0 date aberration in logs
  • From: Matheus de Oliveira <matioli.matheus@xxxxxxxxx>
• postgres 9.0 date aberration in logs
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• 9.1 QUestion -- directory left over after drop database
  • From: Greg Williamson <gwilliamson39@xxxxxxxxx>
• Re: Postgres community version limitaiton - help needed
  • From: ajay kumar <akp123@xxxxxxxxxxx>
• Re: Add tablefunc modules to Postgresql 9.1
  • From: Kevin Duffy <kevind0718@xxxxxxxxx>
• Re: Postgres community version limitaiton - help needed
  • From: Thomas Kellerer <spam_eater@xxxxxxx>
• Re: Postgres community version limitaiton - help needed
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Andrew Barinov <abarinov@xxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Andrew Barinov <abarinov@xxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Add tablefunc modules to Postgresql 9.1
  • From: Tom Lane <tgl@xxxxxxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Andrew Barinov <abarinov@xxxxxxxxx>
• Re: Postgres community version limitaiton - help needed
  • From: Scott Marlowe <scott.marlowe@xxxxxxxxx>
• Add tablefunc modules to Postgresql 9.1
  • From: Kevin Duffy <kevind0718@xxxxxxxxx>
• Postgres community version limitaiton - help needed
  • From: ajay kumar <akp123@xxxxxxxxxxx>
• Postges 9.0 WAL SEGEMENT SIZE is 128 GB for default server configuration.
  • From: girish R G peetle <giri.anamika0@xxxxxxxxx>
• build postgresql problem
  • From: arokyzxc <arokyzxc@xxxxxxxxx>
• Re: postgresql failed to establish a connection to <pg server name>
  • From: "Kevin Grittner" <Kevin.Grittner@xxxxxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Scott Ribe <scott_ribe@xxxxxxxxxxxxxxxx>
• Re: Starting postgres server on mac os x 10.6.8
  • From: Andrew Barinov <abarinov@xxxxxxxxx>