Postgresql General Discussion

• Thread Index

• Re: Problem for restoure data base Postgre
  • From: aspenbr
• Windows 7 Compatibility
  • From: Wong, Beverly
• Re: serial- sequence priveleges
  • From: Adrian Klaver
• Re: serial- sequence priveleges
  • From: Adrian Klaver
• Re: how to measure wal_buffer usage
  • From: Albe Laurenz
• Re: serial- sequence priveleges
  • From: Adrian Klaver
• Re: how to measure wal_buffer usage
  • From: Lonni J Friedman
• Re: Temporal foreign keys
  • From: Andreas Kretschmer
• serial- sequence priveleges
  • From: salah jubeh
• Re: Problem for restoure data base Postgre
  • From: Tom Lane
• Re: Zero-length character breaking query?
  • From: Tom Lane
• Re: Zero-length character breaking query?
  • From: David Johnston
• Re: how to measure wal_buffer usage
  • From: Albe Laurenz
• Re: Optimise PostgreSQL for fast testing
  • From: Simon Riggs
• Re: Problem for restoure data base Postgre
  • From: Alban Hertroys
• Problem for restoure data base Postgre
  • From: BrunoSteven
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Greg Williamson
• Zero-length character breaking query?
  • From: Doug Gorley
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: Indexing MS/Open Office and PDF documents
  • From: Samba
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Filip Rembiałkowski
• Re: Temporal foreign keys
  • From: Jeff Davis
• Commit hits time-out before CommandTimeout
  • From: Ben Schalley
• Re: undo update
  • From: Steve Crawford
• Re: Indexing MS/Open Office and PDF documents
  • From: dennis jenkins
• Re: Indexing MS/Open Office and PDF documents
  • From: Richard Huxton
• Re: Indexing MS/Open Office and PDF documents
  • From: Jeff Davis
• Re: undo update
  • From: Ivan
• Indexing MS/Open Office and PDF documents
  • From: Alexander.Bagerman
• Re: undo update
  • From: Scott Marlowe
• undo update
  • From: Ivan
• Re: yum repository packages 9.0 and 9.1 libpq conflict
  • From: John R Pierce
• Re: psql latex and newlines
  • From: Alvaro Herrera
• How to perform full text search
  • From: Andrus
• Re: Using copy with a file containing blank rows
  • From: Adrian Klaver
• how to measure wal_buffer usage
  • From: Lonni J Friedman
• Re: Backups
  • From: Bret Stern
• Re: Did xpath_table get dropped.
  • From: Rob Sargent
• Using copy with a file containing blank rows
  • From: George Weaver
• Re: Backups
  • From: Albe Laurenz
• Re: Fetch from cursor with indexed sorting
  • From: Tom Lane
• Re: yum repository packages 9.0 and 9.1 libpq conflict
  • From: Tom Lane
• Re: Backups
  • From: Scott Marlowe
• Fetch from cursor with indexed sorting
  • From: Andrey Chursin
• WHERE IN (subselect) versus WHERE IN (1,2,3,)
  • From: Kevin Goess
• Re: Backups
  • From: Bèrto ëd Sèra
• Re: Backups
  • From: Richard Harley
• Re: Backups
  • From: Bèrto ëd Sèra
• Backups
  • From: Richard Harley
• Re: copy in date string "00-00-00 00:00:00"
  • From: Martin Gregorie
• Re: pg_role vs. pg_shadow or pg_user
  • From: Alexander Reichstadt
• Re: yum repository packages 9.0 and 9.1 libpq conflict
  • From: John R Pierce
• Re: yum repository packages 9.0 and 9.1 libpq conflict
  • From: Devrim GÜNDÜZ
• Re: permission denied to create extension "ltree" Must be superuser to create this extension.
  • From: Abel Abraham Camarillo Ojeda
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: permission denied to create extension "ltree" Must be superuser to create this extension.
  • From: krzf83@xxxxxxxxx
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Scott Marlowe
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Scott Marlowe
• yum repository packages 9.0 and 9.1 libpq conflict
  • From: John R Pierce
• Re: copy in date string "00-00-00 00:00:00"
  • From: Mark Phillips
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: Did xpath_table get dropped.
  • From: Tom Lane
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Scott Marlowe
• Did xpath_table get dropped.
  • From: Rob Sargent
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: copy in date string "00-00-00 00:00:00"
  • From: Scott Marlowe
• Re: copy in date string "00-00-00 00:00:00"
  • From: Andy Colson
• Re: copy in date string "00-00-00 00:00:00"
  • From: Andy Colson
• Re: copy in date string "00-00-00 00:00:00"
  • From: Scott Marlowe
• copy in date string "00-00-00 00:00:00"
  • From: Mark Phillips
• Re: xlog corruption
  • From: Jeff Davis
• Re: Searching email, Full Text Search prefix, not expected results
  • From: Daniel Vázquez
• Re: Upgrade questions
  • From: Scott Marlowe
• Re: pg_role vs. pg_shadow or pg_user
  • From: Tom Lane
• Re: pg_role vs. pg_shadow or pg_user
  • From: Mike Blackwell
• pg_role vs. pg_shadow or pg_user
  • From: Alexander Reichstadt
• Re: Searching email, Full Text Search prefix, not expected results
  • From: Tom Lane
• Re: Upgrade questions
  • From: John R Pierce
• Re: Upgrade questions
  • From: Scott Marlowe
• Re: Upgrade questions
  • From: John R Pierce
• Re: COPY and indices?
  • From: François Beausoleil
• Re: Upgrade questions
  • From: Steve Crawford
• Re: COPY and indices?
  • From: Merlin Moncure
• Re: Upgrade questions
  • From: John R Pierce
• Searching email, Full Text Search prefix, not expected results
  • From: Daniel Vázquez
• Re: COPY and indices?
  • From: François Beausoleil
• Re: Alter Column from inet to inet[]
  • From: Tom Lane
• Alter Column from inet to inet[]
  • From: Alex -
• Re: Upgrade questions
  • From: Carson Gross
• Re: Upgrade questions
  • From: Bret Stern
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Stefan Keller
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Thomas Kellerer
• Re: Ways to edit users and permissions for database
  • From: Alexander Reichstadt
• Re: Ways to edit users and permissions for database
  • From: Adrian Klaver
• provide pg_get_notifications()
  • From: maxxedit@xxxxxxxxx
• Re: Frontend/Backend protocol question.
  • From: Albe Laurenz
• Re: Ways to edit users and permissions for database
  • From: Alexander Reichstadt
• Re: Ways to edit users and permissions for database
  • From: John R Pierce
• Ways to edit users and permissions for database
  • From: Alexander Reichstadt
• Re: Interesting article, Facebook woes using MySQL
  • From: Martijn van Oosterhout
• Re: Upgrade questions
  • From: John R Pierce
• Re: Upgrade questions
  • From: Carson Gross
• Re: Upgrade questions
  • From: Carson Gross
• Re: restore_command is not running on my standby
  • From: Fujii Masao
• restore_command is not running on my standby
  • From: Joseph Shraibman
• Re: Upgrade questions
  • From: John R Pierce
• Re: Upgrade questions
  • From: Carson Gross
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Kiriakos Georgiou
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: John R Pierce
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Samba
• Re: Matching on keyword or phrases within a field that is delimited with an "or" operator "|"
  • From: Jim Ostler
• Re: Upgrade questions
  • From: Carson Gross
• Re: Allowing Other Users to Alter a Table
  • From: Scott Marlowe
• Allowing Other Users to Alter a Table
  • From: Jerry Richards
• Re: COPY and indices?
  • From: Merlin Moncure
• Re: COPY and indices?
  • From: Scott Marlowe
• Re: COPY and indices?
  • From: François Beausoleil
• Re: COPY and indices?
  • From: Merlin Moncure
• Re: How to find compiled-in default port number?
  • From: Adrian Klaver
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Vick Khera
• Re: How to find compiled-in default port number?
  • From: Martin Gregorie
• Frontend/Backend protocol question.
  • From: Dmitriy Igrishin
• How to find compiled-in default port number?
  • From: Виктор Егоров
• Re: COPY and indices?
  • From: hamann . w
• Re: COPY and indices?
  • From: Scott Marlowe
• Re: COPY and indices?
  • From: Ondrej Ivanič
• COPY and indices?
  • From: François Beausoleil
• Re: Upgrade questions
  • From: John R Pierce
• Re: Calculated update
  • From: Bret Stern
• Re: Calculated update
  • From: Bosco Rama
• Re: Matching on keyword or phrases within a field that is delimited with an "or" operator "|"
  • From: Martin Gregorie
• Re: Calculated update
  • From: Rob Sargent
• Calculated update
  • From: Bret Stern
• Re: Matching on keyword or phrases within a field that is delimited with an "or" operator "|"
  • From: David Johnston
• Re: Interesting article, Facebook woes using MySQL
  • From: Stefan Keller
• Re: Upgrade questions
  • From: Carson Gross
• Matching on keyword or phrases within a field that is delimited with an "or" operator "|"
  • From: Jim Ostler
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: John R Pierce
• Re: GROUP BY or alternative means to group
  • From: Scott Marlowe
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Nur Hidayat
• Re: GROUP BY or alternative means to group
  • From: Alexander Reichstadt
• Re: Upgrade questions
  • From: John R Pierce
• Re: full text search and ILIKE type clauses.
  • From: Pavel Stehule
• Re: full text search and ILIKE type clauses.
  • From: Tim Uckun
• Re: GROUP BY or alternative means to group
  • From: Scott Marlowe
• Re: GROUP BY or alternative means to group
  • From: Alexander Reichstadt
• Re: GROUP BY or alternative means to group
  • From: Kiriakos Georgiou
• Solved [Re: GROUP BY or alternative means to group]
  • From: Alexander Reichstadt
• Re: GROUP BY or alternative means to group
  • From: Bartosz Dmytrak
• Re: full text search and ILIKE type clauses.
  • From: mgould
• Re: Upgrade questions
  • From: Tim Uckun
• Re: full text search and ILIKE type clauses.
  • From: Tim Uckun
• GROUP BY or alternative means to group
  • From: Alexander Reichstadt
• Upgrade questions
  • From: Carson Gross
• Re: Return keys for values with dot-separation in joined statements
  • From: Alexander Reichstadt
• Re: Return keys for values with dot-separation in joined statements
  • From: Tom Lane
• Return keys for values with dot-separation in joined statements
  • From: Alexander Reichstadt
• fsync default setting and version
  • From: Ivan Sergio Borgonovo
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Alban Hertroys
• Re: Error installing postgresq91-python package
  • From: PgSQL
• Re: Error installing postgresq91-python package
  • From: Martin Gregorie
• Re: full text search and ILIKE type clauses.
  • From: mgould
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Albe Laurenz
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Nur Hidayat
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Nur Hidayat
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: John R Pierce
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Nur Hidayat
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: full text search and ILIKE type clauses.
  • From: Tim Uckun
• Re: full text search and ILIKE type clauses.
  • From: Tom Lane
• full text search and ILIKE type clauses.
  • From: Tim Uckun
• Re: Error installing postgresq91-python package
  • From: Adrian Klaver
• Re: Error installing postgresq91-python package
  • From: PgSQL
• Re: Error installing postgresq91-python package
  • From: PgSQL
• Re: Parse message is not generating a ParseOk response
  • From: Tom Lane
• Parse message is not generating a ParseOk response
  • From: Maurício Linhares
• Re: permission denied to create extension "ltree" Must be superuser to create this extension.
  • From: Sergey Konoplev
• Re: Error installing postgresq91-python package
  • From: Martin Gregorie
• Re: Error installing postgresq91-python package
  • From: Adrian Klaver
• Re: Error installing postgresq91-python package
  • From: PgSQL
• Re: Error installing postgresq91-python package
  • From: Adrian Klaver
• Re: Error installing postgresq91-python package
  • From: PgSQL
• permission denied to create extension "ltree" Must be superuser to create this extension.
  • From: krzf83@xxxxxxxxx
• Re: Single postgres for Multiple application
  • From: Twaha Daudi
• Re: Single postgres for Multiple application
  • From: Thomas Kellerer
• Single postgres for Multiple application
  • From: Twaha Daudi
• Re: [pgsql-cluster-hackers] advice on Replication for a Specific Scenario
  • From: Donald Kerr
• Re: Regarding NOTIFY
  • From: Kiriakos Georgiou
• Re: Regarding NOTIFY
  • From: Chris Travers
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Francisco Figueiredo Jr.
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Randy Ficker
• Re: Question on datatypes returned for "select oid, typname from pg_type"
  • From: Gavin Flower
• Re: Question on datatypes returned for "select oid, typname from pg_type"
  • From: Tom Lane
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Francisco Figueiredo Jr.
• Re: Question on datatypes returned for "select oid, typname from pg_type"
  • From: Tom Lane
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Randy Ficker
• Question on datatypes returned for "select oid, typname from pg_type"
  • From: Alexander Reichstadt
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Francisco Figueiredo Jr.
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Randy Ficker
• Timeout Transactions on Synchronous Replication Standby Failures
  • From: Yunong Xiao
• Re: 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Marti Raudsepp
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Selena Deckelmann
• 9.1 causing "out of shared memory" error and higher serialization conflicts
  • From: Randy Ficker
• Re: How to erase transaction logs on PostgreSQL
  • From: John R Pierce
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Merlin Moncure
• Regarding NOTIFY
  • From: Bret Stern
• Re: autovacuum and transaction id wraparound
  • From: Scott Marlowe
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Andy Colson
• Re: How to erase transaction logs on PostgreSQL
  • From: Frank Church
• Re: autovacuum and transaction id wraparound
  • From: pawel_kukawski
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Merlin Moncure
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: mgould
• Re: How to erase transaction logs on PostgreSQL
  • From: Simon Riggs
• Re: How to erase transaction logs on PostgreSQL
  • From: Guillaume Lelarge
• Re: how to return the last inserted identity column value
  • From: Ondrej Ivanič
• Re: Synchronous replication + Fusion-io = waste of money OR significant performance boost? (compared to normal SATA-based SSD-disks)?
  • From: Ondrej Ivanič
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Simon Riggs
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Scott Marlowe
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: dennis jenkins
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Andy Colson
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Scott Marlowe
• Call for Google Summer of Code (GSoC) 2012: Project ideas?
  • From: Stefan Keller
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: [BUGS] Altering a table with a rowtype column
  • From: Mike Blackwell
• Re: How to erase transaction logs on PostgreSQL
  • From: Achilleas Mantzios
• Re: how to return the last inserted identity column value
  • From: Scott Marlowe
• how to return the last inserted identity column value
  • From: mgould
• why no create variable
  • From: mgould
• Re: [BUGS] Altering a table with a rowtype column
  • From: Merlin Moncure
• Re: How to erase transaction logs on PostgreSQL
  • From: Guillaume Lelarge
• Re: FDWs, foreign servers and user mappings
  • From: Guillaume Lelarge
• How to erase transaction logs on PostgreSQL
  • From: Frank Church
• Re: Synchronous replication + Fusion-io = waste of money OR significant performance boost? (compared to normal SATA-based SSD-disks)?
  • From: dennis jenkins
• Re: FDWs, foreign servers and user mappings
  • From: Joe Abbate
• Re: Synchronous replication + Fusion-io = waste of money OR significant performance boost? (compared to normal SATA-based SSD-disks)?
  • From: Merlin Moncure
• Re: Advisory transaction lock for 128-bit space
  • From: Merlin Moncure
• Re: rounding a timestamp to nearest x seconds
  • From: Andy Colson
• Re: autovacuum and transaction id wraparound
  • From: Jens Wilke
• Automatic shadow-table management script
  • From: Anssi Kääriäinen
• Re: Advisory transaction lock for 128-bit space
  • From: Kiriakos Georgiou
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Stuart Bishop
• Timeline switch after rsync of *offline* pgdata?
  • From: hubert depesz lubaczewski
• replay_location meaning in pg_stat_replication
  • From: François Beausoleil
• Re: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: FDWs, foreign servers and user mappings
  • From: Shigeru Hanada
• Re: [Slony1-general] A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Joshua D. Drake
• Re: A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: rounding a timestamp to nearest x seconds
  • From: Daniele Varrazzo
• Re: phantom long-running query (check_postgres.pl reports a long-running query, but the database logs don't show it)
  • From: Aleksey Tsalolikhin
• FDWs, foreign servers and user mappings
  • From: Joe Abbate
• autovacuum and transaction id wraparound
  • From: pawel_kukawski
• Re: Converting stored procedures from SQL Anywhere to PostGres.
  • From: Adrian Klaver
• Re: Show Databases via ODBC
  • From: Bret Stern
• Re: [BUGS] Altering a table with a rowtype column
  • From: Merlin Moncure
• Re: [BUGS] Altering a table with a rowtype column
  • From: Alvaro Herrera
• Re: [BUGS] Altering a table with a rowtype column
  • From: Tom Lane
• Re: Altering a table with a rowtype column
  • From: Merlin Moncure
• Re: Automated Backup Script Help (Linux)
  • From: John R Pierce
• Re: Show Databases via ODBC
  • From: Szymon Guz
• Show Databases via ODBC
  • From: Bret Stern
• Re: Converting stored procedures from SQL Anywhere to PostGres.
  • From: Merlin Moncure
• Re: Automated Backup Script Help (Linux)
  • From: Carlos Mennens
• Re: Automated Backup Script Help (Linux)
  • From: John R Pierce
• Re: Full text search ranking: ordering using index and proximiti ranking with OR queries
  • From: Nicolas Grilly
• Re: Automated Backup Script Help (Linux)
  • From: Andrew Gould
• Re: ts_rank seems very slow (140 ranked documents / second on my machine)
  • From: Nicolas Grilly
• Converting stored procedures from SQL Anywhere to PostGres.
  • From: mgould
• Re: Advisory transaction lock for 128-bit space
  • From: Bill Moran
• Automated Backup Script Help (Linux)
  • From: Carlos Mennens
• Re: corrupted table postgresql 8.3
  • From: Matteo Sgalaberni
• Re: corrupted table postgresql 8.3
  • From: Merlin Moncure
• Re: Full text search ranking: ordering using index and proximiti ranking with OR queries
  • From: Andrey Chursin
• Advisory transaction lock for 128-bit space
  • From: Andrey Chursin
• Re: Altering a table with a rowtype column
  • From: Merlin Moncure
• Re: Altering a table with a rowtype column
  • From: Mike Blackwell
• Re: Altering a table with a rowtype column
  • From: Merlin Moncure
• Altering a table with a rowtype column
  • From: Mike Blackwell
• Re: ERROR: could not find tuple for trigger 37463634
  • From: Tom Lane
• Re: Full text search ranking: ordering using index and proximiti ranking with OR queries
  • From: Nicolas Grilly
• Re: Fixing the loss of 'template1'
  • From: Tom Lane
• Re: ERROR: could not find tuple for trigger 37463634
  • From: mdione.ext
• Re: Fixing the loss of 'template1'
  • From: Tom Lane
• Re: Fixing the loss of 'template1'
  • From: Steve Clark
• Re: Fixing the loss of 'template1'
  • From: Adrian Klaver
• Re: Fixing the loss of 'template1'
  • From: Adrian Klaver
• Re: Fixing the loss of 'template1'
  • From: Martin Gregorie
• Re: ERROR: could not find tuple for trigger 37463634
  • From: Tom Lane
• Re: Fixing the loss of 'template1'
  • From: Adrian Klaver
• rounding a timestamp to nearest x seconds
  • From: Andy Colson
• Re: Fixing the loss of 'template1'
  • From: Gary Chambers
• Re: Fixing the loss of 'template1'
  • From: Marti Raudsepp
• Re: Fixing the loss of 'template1'
  • From: Gary Chambers
• Fixing the loss of 'template1'
  • From: Martin Gregorie
• Re: SQL Normalization Thought
  • From: dennis jenkins
• Re: ERROR: could not find tuple for trigger 37463634
  • From: mdione.ext
• SQL Normalization Thought
  • From: David Johnston
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Martin Gregorie
• Re: ERROR: could not find tuple for trigger 37463634
  • From: mdione.ext
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Sergey Konoplev
• ERROR: could not find tuple for trigger 37463634
  • From: mdione.ext
• Synchronous replication + Fusion-io = waste of money OR significant performance boost? (compared to normal SATA-based SSD-disks)?
  • From: Joel Jacobson
• A 154 GB table swelled to 527 GB on the Slony slave. How to compact it?
  • From: Aleksey Tsalolikhin
• Re: Single server multiple databases - extension
  • From: Brian Trudal
• Re: corrupted table postgresql 8.3
  • From: Matteo Sgalaberni
• Re: replication between US <-> EU
  • From: Ondrej Ivanič
• Re: Single server multiple databases - extension
  • From: Tom Lane
• Re: Single server multiple databases - extension
  • From: Brian Trudal
• Re: replication between US <-> EU
  • From: John R Pierce
• replication between US <-> EU
  • From: Ondrej Ivanič
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Chris Angelico
• Re: Unable to write inside TEMP environment variable path
  • From: hello_world
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Tom Lane
• Re: Single server multiple databases - extension
  • From: Bartosz Dmytrak
• Re: corrupted table postgresql 8.3
  • From: Tomas Vondra
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Chris Angelico
• corrupted table postgresql 8.3
  • From: Matteo Sgalaberni
• Re: Single server multiple databases - extension
  • From: Brian Trudal
• Re: Unhelpful initdb error message
  • From: Bosco Rama
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Complex transactions without using plPgSQL Functions. It is possible?
  • From: Adrian Klaver
• Complex transactions without using plPgSQL Functions. It is possible?
  • From: Andre Lopes
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: dennis jenkins
• Re: Adding a lot of tables
  • From: Raymond O'Donnell
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Bosco Rama
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Magnus Hagander
• Re: Unhelpful initdb error message
  • From: Thom Brown
• pg_dump : no tables were found.
  • From: Piyush Lenka
• Re: what Linux to run
  • From: Gavin Flower
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Adding a lot of tables
  • From: jan.musial
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Thom Brown
• Re: Unhelpful initdb error message
  • From: Adrian Klaver
• Re: Unhelpful initdb error message
  • From: Tom Lane
• Unhelpful initdb error message
  • From: Thom Brown
• Re: [ADMIN] pg_dump : no tables were found.
  • From: Julien Rouhaud
• Re: Lost data Folder, but have WAL files--- How to recover the database ?? Windows
  • From: Simon Riggs
• ANALYSE on top-level of partitioned tables - required?
  • From: Toby Corkindale
• Re: Lost data Folder, but have WAL files--- How to recover the database ?? Windows
  • From: Chris Travers
• Single server multiple databases - extension
  • From: Brian Trudal
• Lost data Folder, but have WAL files--- How to recover the database ?? Windows
  • From: chinnaobi
• Re: Memory usage and configuration settings
  • From: Merlin Moncure
• Re: Return unknown resultset from a function
  • From: Merlin Moncure
• Re: Memory usage and configuration settings
  • From: Tom Lane
• Re: Memory usage and configuration settings
  • From: Mike C
• Re: Return unknown resultset from a function
  • From: Tom Lane
• Re: Memory usage and configuration settings
  • From: Tom Lane
• Re: what Linux to run
  • From: mgould
• Re: Return unknown resultset from a function
  • From: Merlin Moncure
• Non inheritable check constraint
  • From: Clodoaldo Neto
• Memory usage and configuration settings
  • From: Mike C
• Re: what Linux to run
  • From: r d
• Determine dead files
  • From: Andreas Brandl
• Re: atoi-like function: is there a better way to do this?
  • From: Tom Molesworth
• Re: SELECT FOR UPDATE could see commited trasaction partially.
  • From: Kiriakos Georgiou
• SELECT FOR UPDATE could see commited trasaction partially.
  • From: Sam Wong
• Re: what Linux to run
  • From: Brent Wood
• Re: what Linux to run
  • From: Gavin Flower
• Create topology from a shape file
  • From: ArArgyridis
• Re: atoi-like function: is there a better way to do this?
  • From: David Johnston
• Re: atoi-like function: is there a better way to do this?
  • From: Chris Angelico
• Re: atoi-like function: is there a better way to do this?
  • From: Tom Molesworth
• Re: atoi-like function: is there a better way to do this?
  • From: Chris Angelico
• Re: atoi-like function: is there a better way to do this?
  • From: David Johnston
• Re: atoi-like function: is there a better way to do this?
  • From: Chris Angelico
• atoi-like function: is there a better way to do this?
  • From: Chris Angelico
• Re: Return unknown resultset from a function
  • From: Rory Campbell-Lange
• Re: Return unknown resultset from a function
  • From: Rory Campbell-Lange
• Re: || versus concat( ), diff behavior
  • From: Tom Lane
• Re: Return unknown resultset from a function
  • From: David Johnston
• Re: Return unknown resultset from a function
  • From: Pavel Stehule
• Return unknown resultset from a function
  • From: Jan Meyland Andersen
• Re: || versus concat( ), diff behavior
  • From: David Johnston
• Re: || versus concat( ), diff behavior
  • From: c k
• Create topology from a shape file
  • From: ArArgyridis
• Re: what Linux to run
  • From: Devrim GÜNDÜZ
• Re: what Linux to run
  • From: Scott Marlowe
• Re: what Linux to run
  • From: Chris Travers
• Re: what Linux to run
  • From: John R Pierce
• Re: what Linux to run
  • From: Chris Travers
• Re: what Linux to run
  • From: Chris Angelico
• Re: what Linux to run
  • From: Jon Nelson
• Re: what Linux to run
  • From: David Boreham
• Re: what Linux to run
  • From: Tom Lane
• Re: what Linux to run
  • From: David Boreham
• Re: what Linux to run
  • From: John R Pierce
• Re: what Linux to run
  • From: Gavin Flower
• Mix characters with utf-8 characters on the same query
  • From: Daniel Vázquez
• Re: Problems with non use of indexes
  • From: Scott Marlowe
• Re: what Linux to run
  • From: Scott Marlowe
• Re: what Linux to run
  • From: Scott Marlowe
• Re: what Linux to run
  • From: Scott Marlowe
• Re: what Linux to run
  • From: Leif Biberg Kristensen
• Re: Content management system to build web site with PostgreSql, should it be WordPress
  • From: Raymond O'Donnell
• Re: what Linux to run
  • From: Chris Angelico
• Re: what Linux to run
  • From: Raymond O'Donnell
• Content management system to build web site with PostgreSql, should it be WordPress
  • From: Andrus
• Re: what Linux to run
  • From: Chris Travers
• Re: what Linux to run
  • From: Leif Biberg Kristensen
• Re: what Linux to run
  • From: Gavin Flower
• Re: role missing in dump
  • From: Thomas Prause
• Re: Restoring selected records from backup file
  • From: Adrian Klaver
• Re: role missing in dump
  • From: Adrian Klaver
• role missing in dump
  • From: Thomas Prause
• Re: || versus concat( ), diff behavior
  • From: David Johnston
• Restoring selected records from backup file
  • From: Piyush Lenka
• Re: || versus concat( ), diff behavior
  • From: Philip Couling
• Re: || versus concat( ), diff behavior
  • From: Ben Chobot
• || versus concat( ), diff behavior
  • From: david.sahagian
• Re: concatenating text and bytea
  • From: Tom Lane
• concatenating text and bytea
  • From: Vincent de Phily
• Re: Opposite function of hstore each function
  • From: ChoonSoo Park
• Re: Opposite function of hstore each function
  • From: Bosco Rama
• Opposite function of hstore each function
  • From: ChoonSoo Park
• Re: what Linux to run
  • From: Volodymyr Kostyrko
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: Adrian Klaver
• Re: Problems with non use of indexes
  • From: Tyler Durden
• Re: Problems with non use of indexes
  • From: Tomas Vondra
• Re: Problems with non use of indexes
  • From: Tyler Durden
• Re: Problems with non use of indexes
  • From: Tomas Vondra
• Re: Problems with non use of indexes
  • From: Tyler Durden
• Re: Problems with non use of indexes
  • From: Tomas Vondra
• Problems with non use of indexes
  • From: Tyler Durden
• Re: Yearly date comparison?
  • From: Vincent Veyron
• Re: Quoted strings on CLI
  • From: Alexander Reichstadt
• Re: Quoted strings on CLI
  • From: Pavel Stehule
• Quoted strings on CLI
  • From: Alexander Reichstadt
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: chinnaobi
• Re: Split read/write queries between 2 servers (one master and one slave with streaming replication)?
  • From: Adam Cornett
• Split read/write queries between 2 servers (one master and one slave with streaming replication)?
  • From: Benjamin Henrion
• pg_upgrade + streaming replication ?
  • From: Lonni J Friedman
• Re: "Compressed data is corrupt"
  • From: Tom Lane
• Re: 2 x duplicate key value violation: which exception comes first ?
  • From: Tom Lane
• Re: 100% cpu usage on some postmaster processes kill the complete database
  • From: Scott Marlowe
• Re: 100% cpu usage on some postmaster processes kill the complete database
  • From: Paul Dunkler
• Re: 100% cpu usage on some postmaster processes kill the complete database
  • From: Richard Huxton
• Re: 100% cpu usage on some postmaster processes kill the complete database
  • From: Paul Dunkler
• Re: Ident authentication failed for user
  • From: John R Pierce
• Re: Ident authentication failed for user
  • From: Ruben Blanco
• Re: Problem with initdb and two versions on one server?
  • From: Chris McCormick
• Re: Ident authentication failed for user
  • From: John R Pierce
• Re: accumulating handles problem on machine running postgresql
  • From: Adam Bruss
• Ident authentication failed for user
  • From: Ruben Blanco
• Re: 100% cpu usage on some postmaster processes kill the complete database
  • From: Richard Huxton
• 100% cpu usage on some postmaster processes kill the complete database
  • From: Paul Dunkler
• Re: what Linux to run
  • From: Scott Marlowe
• Re: Allowed DML on replicas?
  • From: Guillaume Lelarge
• "Compressed data is corrupt"
  • From: Matthias Leisi
• Re: Privilege on schema 'public' not revokable
  • From: Vincent de Phily
• 2 x duplicate key value violation: which exception comes first ?
  • From: Marc Mamin
• Allowed DML on replicas?
  • From: François Beausoleil
• Re: what Linux to run
  • From: Ivan Voras
• Re: what Linux to run
  • From: Ivan Voras
• Re: what Linux to run
  • From: Vincent Veyron
• Re: "invalid memory alloc request size" + "Could not open file "pg_clog/XXXX"
  • From: Albe Laurenz
• Re: PickSplit method of 2 columns ... error
  • From: Tim Wilson
• Re: Re: One transaction by connection - commit subdetails without release master transaction?
  • From: Ben Chobot
• Re: Re: One transaction by connection - commit subdetails without release master transaction?
  • From: Alban Hertroys
• Re: Valid Input Syntax for Type DATE
  • From: Rich Shepard
• Re: Re: One transaction by connection - commit subdetails without release master transaction?
  • From: Ben Chobot
• Re: Privilege on schema 'public' not revokable
  • From: Tom Lane
• Re: Calling Functions With OUT paramaters
  • From: Raymond O'Donnell
• Re: Privilege on schema 'public' not revokable
  • From: David Johnston
• Privilege on schema 'public' not revokable
  • From: Vincent de Phily
• Re: Valid Input Syntax for Type DATE
  • From: Andrew Gould
• Re: Valid Input Syntax for Type DATE
  • From: Andy Colson
• Re: Valid Input Syntax for Type DATE
  • From: Andy Colson
• Re: accumulating handles problem on machine running postgresql
  • From: dennis jenkins
• Re: what Linux to run
  • From: Scott Marlowe
• Valid Input Syntax for Type DATE
  • From: Rich Shepard
• PQputCopyData buffer limit
  • From: sujayr06
• Re: what Linux to run
  • From: Gary Chambers
• "invalid memory alloc request size" + "Could not open file "pg_clog/XXXX"
  • From: scheu_postgresql
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: Adrian Klaver
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: chinnaobi
• Re: Client encoding not the same as the db encoding
  • From: Adrian Klaver
• Re: version controlling postgresql code
  • From: akp geek
• Re: what Linux to run
  • From: Gary Chambers
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: dhaval jaiswal
• Arbitrary and mixed data types in function
  • From: McGehee, Robert
• Calling Functions With OUT paramaters
  • From: David Greco
• Re: Client encoding not the same as the db encoding
  • From: Tom Lane
• Easy way to corrupt a standby database
  • From: Chris Travers
• Re: Client encoding not the same as the db encoding
  • From: Adrian Klaver
• Re: accumulating handles problem on machine running postgresql
  • From: Adam Bruss
• Client encoding not the same as the db encoding
  • From: Clodoaldo Neto
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: chinnaobi
• Re: One transaction by connection - commit subdetails without release master transaction?
  • From: Durumdara
• Re: Error installing postgresq91-python package
  • From: Clodoaldo Neto
• Re: Error installing plpythonu in 9.1
  • From: Clodoaldo Neto
• Re: Correct way for locking a row for long time without blocking another transactions (=nowait)?
  • From: Filip Rembiałkowski
• Re: Yearly date comparison?
  • From: Albe Laurenz
• Re: what Linux to run
  • From: Chris Angelico
• debugging postgres server memory checker
  • From: Dave Potts
• Re: Correct way for locking a row for long time without blocking another transactions (=nowait)?
  • From: Durumdara
• Yearly date comparison?
  • From: Nick
• Re: what Linux to run
  • From: Scott Marlowe
• Re: what Linux to run
  • From: hamann . w
• Re: synchronous replication: blocking commit on the master
  • From: Fujii Masao
• Partial matches on full text searches.
  • From: Tim Uckun
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Scott Marlowe
• Re: strategies for dealing with frequently updated tables
  • From: Dave Vitek
• Re: synchronous replication: blocking commit on the master
  • From: Jameison Martin
• Re: strategies for dealing with frequently updated tables
  • From: Andy Colson
• Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Lummis, Patrick J
• Re: accumulating handles problem on machine running postgresql
  • From: dennis jenkins
• Re: Error installing postgresq91-python package
  • From: Devrim GÜNDÜZ
• Re: psql: invalid connection option "client_encoding"
  • From: Devrim GÜNDÜZ
• Re: Error installing plpythonu in 9.1
  • From: Devrim GÜNDÜZ
• Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Adrian Klaver
• Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Bartosz Dmytrak
• Re: what Linux to run
  • From: Rich Shepard
• Re: how to create data on the fly?
  • From: David Johnston
• Error installing plpythonu in 9.1
  • From: Clodoaldo Neto
• Re: version controlling postgresql code
  • From: Greg Williamson
• Re: what Linux to run
  • From: hamann . w
• Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Lummis, Patrick J
• Re: how to create data on the fly?
  • From: Bartosz Dmytrak
• Re: synchronous replication: blocking commit on the master
  • From: Adrian Klaver
• Re: Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Bartosz Dmytrak
• Re: strategies for dealing with frequently updated tables
  • From: Dave Vitek
• Stored Procedure Record Updates using For Loops - Postgres 8.1
  • From: Lummis, Patrick J
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: version controlling postgresql code
  • From: Andy Colson
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• version controlling postgresql code
  • From: akp geek
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Tom Lane
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: what Linux to run
  • From: Steve Atkins
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Ireneusz Pluta
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: what Linux to run
  • From: Rich Shepard
• Re: what Linux to run
  • From: Adam Cornett
• what Linux to run
  • From: mgould
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: hari . fuchs
• psql: invalid connection option "client_encoding"
  • From: Clodoaldo Neto
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: Daniele Varrazzo
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: Marti Raudsepp
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: Daniele Varrazzo
• Re: Problem with initdb and two versions on one server?
  • From: Rainer Pruy
• Re: synchronous replication: blocking commit on the master
  • From: Adrian Klaver
• Re: Problem with initdb and two versions on one server?
  • From: Tom Lane
• Re: synchronous replication: blocking commit on the master
  • From: Jameison Martin
• Problem with initdb and two versions on one server?
  • From: Chris McCormick
• Re: archive_cleanup_command recovery.conf Standby server error
  • From: Adrian Klaver
• Re: accumulating handles problem on machine running postgresql
  • From: Adam Bruss
• Re: accumulating handles problem on machine running postgresql
  • From: Marti Raudsepp
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: Marti Raudsepp
• Error installing postgresq91-python package
  • From: Clodoaldo Neto
• Re: How to get a signal from the database when a INSERT INTO is done?
  • From: hubert depesz lubaczewski
• How to get a signal from the database when a INSERT INTO is done?
  • From: Andre Lopes
• alter user and alter cmd do not have same functions
  • From: Jov
• Re: "canceling autovacuum time"
  • From: Tomas Vondra
• Re: Correct way for locking a row for long time without blocking another transactions (=nowait)?
  • From: Filip Rembiałkowski
• how to create data on the fly?
  • From: bboett
• Correct way for locking a row for long time without blocking another transactions (=nowait)?
  • From: Durumdara
• archive_cleanup_command recovery.conf Standby server error
  • From: chinnaobi
• Re: Does the current user have UPDATE privilege on FOO?
  • From: Lionel Elie Mamane
• Re: strategies for dealing with frequently updated tables
  • From: Andy Colson
• Re: PSQL 9.1 Streaming Replication Windows 2008 64 bit Servers
  • From: chinnaobi
• Re: "canceling autovacuum time"
  • From: Ondrej Ivanič
• Re: accumulating handles problem on machine running postgresql
  • From: John R Pierce
• accumulating handles problem on machine running postgresql
  • From: Adam Bruss
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: synchronous replication: blocking commit on the master
  • From: Adrian Klaver
• xlog corruption
  • From: Jameison Martin
• synchronous replication: blocking commit on the master
  • From: Jameison Martin
• "canceling autovacuum time"
  • From: Jameison Martin
• strategies for dealing with frequently updated tables
  • From: Dave Vitek
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Tom Lane
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Ireneusz Pluta
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Tom Lane
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• PL/Python on Postgres 9.1
  • From: Josh Hemann
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Ireneusz Pluta
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Tom Lane
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Orphaned temp table
  • From: Tom Lane
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Tom Lane
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Stefan Keller
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Orphaned temp table
  • From: Mike Blackwell
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: David Salisbury
• Re: Having a problem with RoR-3.1.1 and Pg-9.1
  • From: Adrian Klaver
• Re: Does the current user have UPDATE privilege on FOO?
  • From: Mike Blackwell
• pg_class.relnamespace NOT IN pg_namespace.oid
  • From: Ireneusz Pluta
• Does the current user have UPDATE privilege on FOO?
  • From: Lionel Elie Mamane
• Having a problem with RoR-3.1.1 and Pg-9.1
  • From: James B. Byrne
• Re: explain and index scan
  • From: Tom Lane
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Andrew Sullivan
• Re: Default PostgreSQL server encoding - Change to unicode (utf8)
  • From: Adrian Klaver
• Re: PSQL 9.1 Streaming Replication Windows 2008 64 bit Servers
  • From: Adrian Klaver
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Andy Colson
• Re: problem setting up
  • From: Adrian Klaver
• Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Merlin Moncure
• problem setting up
  • From: hamann . w
• PSQL 9.1 Streaming Replication Windows 2008 64 bit Servers
  • From: chinnaobi
• Re: explain and index scan
  • From: Albe Laurenz
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Chris Travers
• Re: Default PostgreSQL server encoding - Change to unicode (utf8)
  • From: Léa Massiot
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Stefan Keller
• Re: A better COPY?
  • From: Tim Uckun
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Chris Travers
• Re: A better COPY?
  • From: Marti Raudsepp
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: A better COPY?
  • From: Alban Hertroys
• A better COPY?
  • From: Tim Uckun
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Scott Marlowe
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Stefan Keller
• Re: Constant value for a partitioned table query inside a plpgsql function
  • From: Clodoaldo Neto
• Re: How to debugging a an external C function(IMMUTABLE STRICT )
  • From: Tom Lane
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Karsten Hilbert
• Constant value for a partitioned table query inside a plpgsql function
  • From: Clodoaldo Neto
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Andy Colson
• Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Jayashankar K B
• How to debugging a an external C function(IMMUTABLE STRICT )
  • From: Dave Potts
• Re: Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Scott Marlowe
• Four issues why "old elephants" lack performance: Explanation sought Four issues why "old elephants" lack performance: Explanation sought
  • From: Stefan Keller
• What effect does destroying database related threads have on system resources?
  • From: Frank Church
• Re: Stability in Windows?
  • From: Gavin Flower
• Re: Rails & pg setup question
  • From: Daniel Podlejski
• Re: Rails & pg setup question
  • From: Joshua D. Drake
• Rails & pg setup question
  • From: Scott Ribe
• Re: How to typecast an integer into a timestamp?
  • From: Jasen Betts
• Re: Behavior of subselects in target lists and order by
  • From: Jasen Betts
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Naoko Reeves
• Re: Pull the Trigger and Where's the SQL?
  • From: John R Pierce
• Re: Behavior of subselects in target lists and order by
  • From: John R Pierce
• Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Tom Lane
• Behavior of subselects in target lists and order by
  • From: amit sehas
• Pull the Trigger and Where's the SQL?
  • From: Ched Cheatham
• Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Jayashankar K B
• Disk file effects of delete and vacuum
  • From: Clodoaldo Neto
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Re: When I try to connect to a database, I get the following error : psql teleflowdb8
  • From: Adrian Klaver
• Re: Maxium Share Memory in Debian 64bit
  • From: Scott Marlowe
• Re: Stability in Windows?
  • From: Scott Marlowe
• Re: Re: When I try to connect to a database, I get the following error : psql teleflowdb8
  • From: Scott Marlowe
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Scott Marlowe
• explain and index scan
  • From: psql
• Re: When I try to connect to a database, I get the following error : psql teleflowdb8
  • From: seha
• Re: Stability in Windows?
  • From: Igor Neyman
• Re: Maxium Share Memory in Debian 64bit
  • From: John R Pierce
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Maxium Share Memory in Debian 64bit
  • From: Prashant Bharucha
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Tom Lane
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Scott Marlowe
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: Regular expression character escape
  • From: Tom Lane
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Tom Lane
• Re: invalid memory alloc request size 1765277700 Error Question
  • From: Garrett Murphy
• Re: Regular expression character escape
  • From: Ronan Dunklau
• Re: Regular expression character escape
  • From: Heiko Wundram
• Re: Regular expression character escape
  • From: Ronan Dunklau
• Re: Stability in Windows?
  • From: Magnus Hagander
• Re: Regular expression character escape
  • From: Heiko Wundram
• Re: Stability in Windows?
  • From: Serge Fonville
• Re: Stability in Windows?
  • From: Adrian Klaver
• Re: Stability in Windows?
  • From: Scott Marlowe
• Re: Regular expression character escape
  • From: Ronan Dunklau
• Re: Stability in Windows?
  • From: Durumdara
• Re: Stability in Windows?
  • From: Serge Fonville
• Re: Stability in Windows?
  • From: mgould
• Stability in Windows?
  • From: Durumdara
• Re: Regular expression character escape
  • From: David Johnston
• Re: Having a problem with RoR-3.1.1 and Pg-0.1
  • From: Adrian Klaver
• Re: problem trying to create a temp table
  • From: Adrian Klaver
• Having a problem with RoR-3.1.1 and Pg-0.1
  • From: James B. Byrne
• Re: Measuring replication lag time
  • From: Samba
• Re: Configuring for very slow I/O
  • From: Vick Khera
• Re: problem trying to create a temp table
  • From: Richard Huxton
• Re: problem trying to create a temp table
  • From: Richard Huxton
• Re: problem trying to create a temp table
  • From: mgould
• Re: problem trying to create a temp table
  • From: Andrew Gould
• Re: problem trying to create a temp table
  • From: Andrew Gould
• Re: problem trying to create a temp table
  • From: mgould
• Re: problem trying to create a temp table
  • From: Richard Huxton
• problem trying to create a temp table
  • From: mgould
• Configuring for very slow I/O
  • From: A B
• Regular expression character escape
  • From: Ronan Dunklau
• invalid memory alloc request size 1765277700 Error Question
  • From: Naoko Reeves
• Re: Optimise PostgreSQL for fast testing
  • From: Simon Riggs
• Re: COPY TO File: Using dynamic file name in stored procedure
  • From: Albe Laurenz
• Re: Problemas com client_encoding ?
  • From: Richard Huxton
• Re: Optimise PostgreSQL for fast testing
  • From: Alban Hertroys
• Problemas com client_encoding ?
  • From: Emanuel Araújo
• Re: Optimise PostgreSQL for fast testing
  • From: Adrian Klaver
• Re: Optimise PostgreSQL for fast testing
  • From: Scott Marlowe
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Optimise PostgreSQL for fast testing
  • From: Greg Smith
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: psql latex and newlines
  • From: Harvey, Allan AC
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: Optimise PostgreSQL for fast testing
  • From: Dmytrii Nagirniak
• Re: Optimise PostgreSQL for fast testing
  • From: Scott Marlowe
• Re: Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Merlin Moncure
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Upgrade to 9.1 causing function problem
  • From: Igor Polishchuk
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Jayashankar K B
• Re: Upgrade to 9.1 causing function problem
  • From: John R Pierce
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: [PERFORM] Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Tom Lane
• Re: Upgrade to 9.1 causing function problem
  • From: Rob Sargent
• Disable-spinlocks while compiling postgres 9.1 for ARM Cortex A8
  • From: Jayashankar K B
• Re: Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: Upgrade to 9.1 causing function problem
  • From: Adrian Klaver
• Upgrade to 9.1 causing function problem
  • From: Willem Buitendyk
• Re: Optimise PostgreSQL for fast testing
  • From: Simon Riggs
• Re: Dynamic File Name for COPY TO in Stored Procedure
  • From: Carlos Oliva
• Re: Optimise PostgreSQL for fast testing
  • From: Scott Marlowe
• Re: Optimise PostgreSQL for fast testing
  • From: David Salisbury
• Re: How to enable thread safety on postgresql 8.3.6
  • From: John R Pierce
• COPY TO File: Using dynamic file name in stored procedure
  • From: Carlos Oliva
• Re: Optimise PostgreSQL for fast testing
  • From: Jack Christensen
• Re: psql latex and newlines
  • From: Wim Bertels
• Re: How to enable thread safety on postgresql 8.3.6
  • From: Albe Laurenz
• Re: Optimise PostgreSQL for fast testing
  • From: Simon Riggs
• Re: Optimise PostgreSQL for fast testing
  • From: Adrian Klaver
• Re: Dynamic File Name for COPY TO in Stored Procedure
  • From: Adrian Klaver
• Dynamic File Name for COPY TO in Stored Procedure
  • From: Carlos Oliva
• Re: Postgresql as main database
  • From: Chris Travers
• Re: Postgresql as main database
  • From: Albe Laurenz
• Re: How to enable thread safety on postgresql 8.3.6
  • From: ultrayoYO
• How to enable thread safety on postgresql 8.3.6
  • From: ultrayoYO