Postgresql General Discussion

• Thread Index

• Re: Search Path vs Synonyms
  • From: Magnus Hagander
• Re: Search Path vs Synonyms
  • From: John R Pierce
• Re: Search Path vs Synonyms
  • From: Matthew Seaborn
• Re: ECPG Deallocate PREPARE statement - bug ?
  • From: Albe Laurenz
• Re: Search Path vs Synonyms
  • From: Albe Laurenz
• service stopping and pg_standby on windows
  • From: Alexandr Varlamov
• Converting SQL to pg
  • From: martin
• Re: synchronous_commit=off doesn't always return immediately
  • From: tomrevam
• A question about pg_standby.
  • From: Tim Uckun
• citext contrib module (building indexes)
  • From: Michael Gould
• Re: user/grant - best practices handling permission in production system
  • From: Greg Stark
• user/grant - best practices handling permission in production system
  • From: Stefano Nichele
• Re: commercial adaptation of postgres
  • From: Brent Wood
• Re: A question on PSQL 8.3 setup
  • From: Jong Chun Park
• Re: 3des key lengths and key management
  • From: Christophe
• Re: 3des key lengths and key management
  • From: Steve Atkins
• Re: 3des key lengths and key management
  • From: Steve Atkins
• uuid contrib don't compile in OpenSolaris
  • From: Emanuel Calvo Franco
• Re: 3des key lengths and key management
  • From: Greg Stark
• Re: commercial adaptation of postgres
  • From: Greg Smith
• Re: ERROR: could not access status of transaction 2495690984
  • From: Greg Smith
• Disable databse listing for non-superuser (\l) ?
  • From: Brian A. Seklecki
• 3des key lengths and key management
  • From: bulk
• Re: ERROR: could not access status of transaction 2495690984
  • From: Bjørn T Johansen
• Re: synchronous_commit=off doesn't always return immediately
  • From: Greg Smith
• Re: table.column in query results?
  • From: Andrew Klaassen
• Re: comparing NEW and OLD (any good this way?)
  • From: Joshua Tolley
• Re: problem with pg_restore?
  • From: Greg Stark
• Re: enabling join_collapse_limit for a single query only
  • From: Matt Harrison
• split string by special characters
  • From: Jan-Erik
• Search Path vs Synonyms
  • From: Matthew Seaborn
• Re: ERROR: unexpected data beyond EOF in block of relation "RelationName"
  • From: Tom Lane
• Re: synchronous_commit=off doesn't always return immediately
  • From: Tom Lane
• Re: comparing NEW and OLD (any good this way?)
  • From: Pavel Stehule
• Re: Copying only incremental records to another DB..
  • From: Scott Ribe
• Re: Copying only incremental records to another DB..
  • From: Phoenix Kiula
• Re: problem with pg_restore?
  • From: Sam Mason
• Re: comparing NEW and OLD (any good this way?)
  • From: Sam Mason
• Re: problem with pg_restore?
  • From: Scott Marlowe
• Re: A question on PSQL 8.3 setup
  • From: Sam Mason
• Re: comparing NEW and OLD (any good this way?)
  • From: Merlin Moncure
• Re: problem with pg_restore?
  • From: Sam Mason
• Re: comparing NEW and OLD (any good this way?)
  • From: Thomas Kellerer
• Re: 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent
  • From: Michael Gould
• Re: comparing NEW and OLD (any good this way?)
  • From: Pavel Stehule
• Re: A question on PSQL 8.3 setup
  • From: Daniel Verite
• Re: comparing NEW and OLD (any good this way?)
  • From: Andreas Wenk
• Re: comparing NEW and OLD (any good this way?)
  • From: Thomas Kellerer
• ECPG Deallocate PREPARE statement - bug ?
  • From: leif
• Re: comparing NEW and OLD (any good this way?)
  • From: Pavel Stehule
• ERROR: unexpected data beyond EOF in block of relation "RelationName"
  • From: Marcin Gon
• comparing NEW and OLD (any good this way?)
  • From: Willy-Bas Loos
• Re: table.column in query results?
  • From: Jasen Betts
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: Jasen Betts
• Re: problem with pg_restore?
  • From: Jasen Betts
• Re: enabling join_collapse_limit for a single query only
  • From: Albe Laurenz
• Re: table.column in query results?
  • From: Albe Laurenz
• PostgreSQL 8.4.0-1 windwos crashes when run without admin privs
  • From: Massa, Harald Armin
• synchronous_commit=off doesn't always return immediately
  • From: tomrevam
• Re: 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent
  • From: Dave Page
• A question on PSQL 8.3 setup
  • From: Jong Chun Park
• Re: 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent
  • From: Magnus Hagander
• Re: 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent
  • From: Steffen Kuhn
• Re: memory leak occur when disconnect database
  • From: tanjunhua
• Re: Problem search on text arrays, using the overlaps (&&) operator
  • From: John Cheng
• Re: Help using SELECT INTO to make schema
  • From: Jeff Davis
• Help using SELECT INTO to make schema
  • From: Robert James
• Re: Can LIKE under utf8 use INDEXes?
  • From: Tom Lane
• Re: Can LIKE under utf8 use INDEXes?
  • From: Andreas Wenk
• Re: Can LIKE under utf8 use INDEXes?
  • From: Andreas Wenk
• Re: Best practices for moving UTF8 databases
  • From: Sam Mason
• Re: Select Column Auditing/Logging
  • From: Sam Mason
• Re: Can LIKE under utf8 use INDEXes?
  • From: Robert James
• Re: Best way to import data in postgresl (not "COPY")
  • From: Sam Mason
• Re: Can LIKE under utf8 use INDEXes?
  • From: Andreas Wenk
• Re: How would I get information regarding update when running for a long time?
  • From: Sam Mason
• plperl spi_prepare and arrays
  • From: Nathan Jahnke
• Re: Can LIKE under utf8 use INDEXes?
  • From: Robert James
• Re: Documentation Improvement suggestions
  • From: Robert James
• Re: Select Column Auditing/Logging
  • From: Jeff Davis
• Re: Select Column Auditing/Logging
  • From: Jeff Davis
• 8.4.0 installer for Windows from EnterpriseDB does not seem to include pgagent
  • From: Knut P. Lehre
• Select Column Auditing/Logging
  • From: Jeremy Brown
• table.column in query results?
  • From: Andrew Klaassen
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Andreas Wenk
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Alvaro Herrera
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Tom Lane
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Andreas Wenk
• Re: Can LIKE under utf8 use INDEXes?
  • From: Tom Lane
• Re: Best way to import data in postgresl (not "COPY")
  • From: Andy Colson
• Re: Can LIKE under utf8 use INDEXes?
  • From: Jeff Davis
• Re: Can LIKE under utf8 use INDEXes?
  • From: Greg Stark
• Best way to import data in postgresl (not "COPY")
  • From: Denis BUCHER
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Alvaro Herrera
• Re: Best practices for moving UTF8 databases
  • From: Justin Pasher
• Can LIKE under utf8 use INDEXes?
  • From: Robert James
• Re: Checkpoint Tuning Question
  • From: tomrevam
• Re: How would I get information regarding update when running for a long time?
  • From: Grzegorz Jaśkiewicz
• enabling join_collapse_limit for a single query only
  • From: groovefillet
• How would I get information regarding update when running for a long time?
  • From: Chris Barnes
• Re: array_agg crash?
  • From: Tom Lane
• Re: Best practices for moving UTF8 databases
  • From: Phoenix Kiula
• Re: array_agg crash?
  • From: Chris Spotts
• Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
  • From: Ow Mun Heng
• Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
  • From: Sim Zacks
• Re: Inserts into sl_log tables timing out (related to the dataloss bug)
  • From: Tom Lane
• Re: Inserts into sl_log tables timing out (related to the dataloss bug)
  • From: Aleksander Kmetec
• Inserts into sl_log tables timing out (related to the dataloss bug)
  • From: Aleksander Kmetec
• Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
  • From: Ow Mun Heng
• Re: Row insertion w/ trigger to another table update causes row insertion to _not_ occur
  • From: Greg Stark
• Re: element from an array by its index
  • From: Sam Mason
• Row insertion w/ trigger to another table update causes row insertion to _not_ occur
  • From: Ow Mun Heng
• Re: suggestion: log_statement = sample
  • From: Janning Vygen
• Re: ERROR: could not access status of transaction 2495690984
  • From: Merlin Moncure
• Re: suggestion: log_statement = sample
  • From: Merlin Moncure
• Re: element from an array by its index
  • From: Merlin Moncure
• Re: killing processes
  • From: Merlin Moncure
• Re: commercial adaptation of postgres
  • From: Merlin Moncure
• Re: killing processes
  • From: Chris Spotts
• Re: killing processes
  • From: David Kerr
• Re: array_agg crash?
  • From: Chris Spotts
• Re: array_agg crash?
  • From: Tom Lane
• Re: killing processes
  • From: Tom Lane
• Re: array_agg crash?
  • From: Chris Spotts
• ERROR: could not access status of transaction 2495690984
  • From: Bjørn T Johansen
• Re: array_agg crash?
  • From: Tom Lane
• Re: array_agg crash?
  • From: Chris Spotts
• Re: suggestion: log_statement = sample
  • From: Tom Lane
• Re: suggestion: log_statement = sample
  • From: Janning Vygen
• Re: killing processes
  • From: David Kerr
• Re: array_agg crash?
  • From: Tom Lane
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Bill Moran
• Re: commercial adaptation of postgres
  • From: Dennis Gearon
• Re: ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: Tom Lane
• Re: element from an array by its index
  • From: Sam Mason
• Re: commercial adaptation of postgres
  • From: bricklen
• Re: ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: Craig Ringer
• Re: array_agg crash?
  • From: Chris Spotts
• array_agg crash
  • From: Spotts, Christopher
• element from an array by its index
  • From: Murat Kabilov
• Re: ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: Tom Lane
• Re: array_agg crash?
  • From: Tom Lane
• Re: suggestion: log_statement = sample
  • From: Tom Lane
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Phoenix Kiula
• Re: Best practices for moving UTF8 databases
  • From: Albe Laurenz
• Re: ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: Craig Ringer
• Re: Full text search in PostgreSQL 8.4 [SOLVED]
  • From: Konstantin Pavlov
• array_agg crash?
  • From: Chris Spotts
• ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: tanjunhua
• ***UNCHECKED*** Re: memory leak occur when disconnect database
  • From: tanjunhua
• Re: Best practices for moving UTF8 databases
  • From: Sam Mason
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Peter Eisentraut
• Re: xml to string, ascii x utf8 conversion
  • From: Peter Eisentraut
• ERROR: could not access status of transaction 2495690984
  • From: Bjørn T Johansen
• checking for temp tables information_schema vs. EXCEPTION
  • From: Ivan Sergio Borgonovo
• Re: suggestion: log_statement = sample
  • From: Janning Vygen
• Re: Best practices for moving UTF8 databases
  • From: Daniel Verite
• Re: suggestion: log_statement = sample
  • From: Janning Vygen
• Re: memory leak occur when disconnect database
  • From: Craig Ringer
• Re: memory leak occur when disconnect database
  • From: tanjunhua
• Re: memory leak occur when disconnect database
  • From: tanjunhua
• Re: killing processes
  • From: Tom Lane
• Re: commercial adaptation of postgres
  • From: Ries van Twisk
• Re: commercial adaptation of postgres
  • From: Christophe
• commercial adaptation of postgres
  • From: Dennis Gearon
• Re: Best practices for moving UTF8 databases
  • From: Phoenix Kiula
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Phoenix Kiula
• Re: Help needed for reading postgres log : RE: Concurrency issue under very heay loads
  • From: Alvaro Herrera
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: Steve Crawford
• Re: killing processes
  • From: David Kerr
• Re: killing processes
  • From: Tom Lane
• Re: killing processes
  • From: Merlin Moncure
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: John R Pierce
• Re: killing processes
  • From: Scott Marlowe
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: Ben Chobot
• Re: Concurrency issue under very heay loads
  • From: Raji Sridar (raji)
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: Scott Marlowe
• killing processes
  • From: David Kerr
• Re: Server Backup: pg_dump vs pg_dumpall
  • From: Greg Williamson
• Help needed for reading postgres log : RE: Concurrency issue under very heay loads
  • From: Raji Sridar (raji)
• Server Backup: pg_dump vs pg_dumpall
  • From: APseudoUtopia
• Re: best practice transitioning from one datatype to another
  • From: CG
• Log timings on Windows 64
  • From: Scott Mead
• Re: suggestion: log_statement = sample
  • From: Joshua D. Drake
• Re: suggestion: log_statement = sample
  • From: Bill Moran
• Re: suggestion: log_statement = sample
  • From: Steve Atkins
• Re: suggestion: log_statement = sample
  • From: Joshua D. Drake
• Re: suggestion: log_statement = sample
  • From: Bill Moran
• Re: suggestion: log_statement = sample
  • From: Greg Sabino Mullane
• xml to string, ascii x utf8 conversion
  • From: Radek Novotný
• Re: Checkpoint Tuning Question
  • From: Dan Armbrust
• Re: Documentation Improvement suggestions
  • From: Martijn van Oosterhout
• Re: Documentation Improvement suggestions
  • From: pepone.onrez
• Re: Documentation Improvement suggestions
  • From: Alvaro Herrera
• Re: Understanding INNER JOIN versus IN subquery
  • From: Grzegorz Jaśkiewicz
• Re: Understanding INNER JOIN versus IN subquery
  • From: Greg Stark
• Re: Understanding sequential versus index scans.
  • From: Greg Stark
• Re: Documentation Improvement suggestions
  • From: Ivan Sergio Borgonovo
• Understanding INNER JOIN versus IN subquery
  • From: Robert James
• Re: timestamp with time zone tutorial
  • From: Adrian Klaver
• Documentation Improvement suggestions
  • From: Robert James
• Re: Understanding sequential versus index scans.
  • From: Robert James
• Re: PostgreSQL Databse Migration to the Latest Version and Help for Database Replication.
  • From: Arndt Lehmann
• Re: Full text search in PostgreSQL 8.4
  • From: Andreas Wenk
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Florian Weimer
• Re: Best practices for moving UTF8 databases
  • From: Martijn van Oosterhout
• Re: [EDIT] Timestamp indicies not being used!
  • From: Pedro Doria Meunier
• Re: [EDIT] Timestamp indicies not being used!
  • From: Alban Hertroys
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Florian Weimer
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Albe Laurenz
• Re: Best practices for moving UTF8 databases
  • From: Albe Laurenz
• Re: timestamp with time zone tutorial
  • From: Karsten Hilbert
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Peter Eisentraut
• Re: timestamp with time zone tutorial
  • From: Dennis Gearon
• Re: First query very slow. Solutions: memory, or settings, or SQL?
  • From: Scott Marlowe
• First query very slow. Solutions: memory, or settings, or SQL?
  • From: Phoenix Kiula
• Re: [PERFORM] Incr/Decr Integer
  • From: Alvaro Herrera
• Re: Autovacuum and pg_stat_reset()
  • From: Alvaro Herrera
• Re: timestamp with time zone tutorial
  • From: Tom Lane
• Re: timestamp with time zone tutorial
  • From: Dennis Gearon
• Re: Best practices for moving UTF8 databases
  • From: Phoenix Kiula
• Re: Should I CLUSTER on PRIMARY KEY
  • From: Sam Mason
• Re: timestamp with time zone tutorial
  • From: Adrian Klaver
• Re: timestamp with time zone tutorial
  • From: Dennis Gearon
• Re: Should I CLUSTER on PRIMARY KEY
  • From: Chris
• Re: Understanding sequential versus index scans.
  • From: Scott Marlowe
• Re: Understanding sequential versus index scans.
  • From: Robert James
• Re: Should I CLUSTER on PRIMARY KEY
  • From: Robert James
• Re: PostgreSQL Databse Migration to the Latest Version and Help for Database Replication.
  • From: Chris
• Re: Should I CLUSTER on PRIMARY KEY
  • From: Chris
• Re: timestamp with time zone tutorial
  • From: Adrian Klaver
• Re: Understanding sequential versus index scans.
  • From: Robert James
• Should I CLUSTER on PRIMARY KEY
  • From: Robert James
• Re: timestamp with time zone tutorial
  • From: Dennis Gearon
• Re: Understanding sequential versus index scans.
  • From: John R Pierce
• Re: Understanding sequential versus index scans.
  • From: Tom Lane
• Re: Understanding sequential versus index scans.
  • From: Greg Stark
• Re: Understanding sequential versus index scans.
  • From: Robert James
• Understanding sequential versus index scans.
  • From: Robert James
• Full text search in PostgreSQL 8.4
  • From: Konstantin Pavlov
• Re: timestamp with time zone tutorial
  • From: Sam Mason
• Re: timestamp with time zone tutorial
  • From: Adrian Klaver
• timestamp with time zone tutorial
  • From: Dennis Gearon
• [SOLVED] Re: Timestamp indicies not being used!
  • From: Pedro Doria Meunier
• Re: PG handling of date expressions
  • From: Sam Mason
• Re: PG handling of date expressions
  • From: Tom Lane
• PostgreSQL Databse Migration to the Latest Version and Help for Database Replication.
  • From: Krishna Komarpant
• PG handling of date expressions
  • From: James B. Byrne
• A powerful feature for easier error finding
  • From: David Andersen
• Re: Timestamp indicies not being used!
  • From: Tom Lane
• Re: Timestamp indicies not being used!
  • From: Sam Mason
• Re: table/view/function access counts
  • From: Sim Zacks
• Re: Timestamp indicies not being used!
  • From: Andreas Kretschmer
• Re: Timestamp indicies not being used!
  • From: Sam Mason
• [EDIT] Timestamp indicies not being used!
  • From: Pedro Doria Meunier
• Re: Timestamp indicies not being used!
  • From: Andreas Kretschmer
• Timestamp indicies not being used!
  • From: Pedro Doria Meunier
• Re: initdb fails on Windows with encoding=LATIN1
  • From: Martijn van Oosterhout
• Re: Best practices for moving UTF8 databases
  • From: Martijn van Oosterhout
• Re: table/view/function access counts
  • From: Pavel Stehule
• table/view/function access counts
  • From: Sim Zacks
• Re: initdb fails on Windows with encoding=LATIN1
  • From: Abraham, Danny
• Re: Function does not exist
  • From: Sim Zacks
• Re: initdb fails on Windows with encoding=LATIN1
  • From: Pavel Stehule
• Re: Best practices for moving UTF8 databases
  • From: Phoenix Kiula
• Re: initdb fails on Windows with encoding=LATIN1
  • From: Diego Schulz
• initdb fails on Windows with encoding=LATIN1
  • From: Abraham, Danny
• Re: uuid-ossp for PostGres 8.4 running on Windows
  • From: Michael Gould
• Re: uuid-ossp for PostGres 8.4 running on Windows
  • From: Sachin Srivastava
• uuid-ossp for PostGres 8.4 running on Windows
  • From: Michael Gould
• Re: Idle in transaction
  • From: Sharma, Sid
• Re: initdb failure on Windows XP
  • From: Serge Fonville
• Re: memory leak occur when disconnect database
  • From: Craig Ringer
• Re: initdb failure on Windows XP
  • From: Sachin Srivastava
• Re: memory leak occur when disconnect database
  • From: Craig Ringer
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: Haszlakiewicz, Eric
• Re: Idle in transaction
  • From: Craig Ringer
• Re: initdb failure on Windows XP
  • From: Joshua D. Drake
• Re: COPY command on windows???
  • From: Thomas Kellerer
• initdb failure on Windows XP
  • From: Sachin Srivastava
• COPY command on windows???
  • From: Andreas
• Re: Please help
  • From: Craig Ringer
• Re: memory leak occur when disconnect database
  • From: Walton Hoops
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Craig Ringer
• Re: Concurrency issue under very heay loads
  • From: Raji Sridar (raji)
• Re: Idle in transaction
  • From: Sharma, Sid
• Re: psql \du [PATCH] extended \du with [+] - was missing
  • From: Andreas Wenk
• Re: Asking for assistance in determining storage requirements
  • From: Scott Marlowe
• Re: change database
  • From: Florian Chis
• Re: Idle in transaction
  • From: Scott Marlowe
• Re: Idle in transaction
  • From: Scott Marlowe
• Re: Idle in transaction
  • From: Richard Huxton
• Re: Asking for assistance in determining storage requirements
  • From: Craig Ringer
• Re: Idle in transaction
  • From: John
• Re: Idle in transaction
  • From: Bill Moran
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: Craig Ringer
• Re: something to suggest indexes
  • From: John
• Re: Concurrency issue under very heay loads
  • From: Craig Ringer
• memory leak occur when disconnect database
  • From: tanjunhua
• Idle in transaction
  • From: Sharma, Sid
• Re: Idle in transaction
  • From: Sharma, Sid
• Re: something to suggest indexes
  • From: Richard Huxton
• Re: [PERFORM] Incr/Decr Integer
  • From: Andres Freund
• Re: [PERFORM] Incr/Decr Integer
  • From: William Scott Jordan
• Re: [PERFORM] Incr/Decr Integer
  • From: William Scott Jordan
• Re: Areca 1680 and RHEL/Centos 5.3 issue
  • From: Greg Smith
• Re: Concurrency issue under very heay loads
  • From: Greg Smith
• Re: Error in insert statement
  • From: Relyea, Mike
• Re: Error in insert statement
  • From: Relyea, Mike
• Re: Error in insert statement
  • From: bricklen
• Re: Error in insert statement
  • From: Thomas Kellerer
• Error in insert statement
  • From: Relyea, Mike
• Re: [PERFORM] Incr/Decr Integer
  • From: Andres Freund
• Re: best practice transitioning from one datatype to another
  • From: CG
• something to suggest indexes
  • From: John
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Alvaro Herrera
• Re: Please help
  • From: Yuriy Rusinov
• Create (function, procedure) and trigger to increment a counter
  • From: Chris Barnes
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Florian Weimer
• Re: Asking for assistance in determining storage requirements
  • From: Alan McKay
• Please help
  • From: Roseller A. Romanos
• Re: suggestion: log_statement = sample
  • From: Janning Vygen
• Re: Using the geqo
  • From: Ms swati chande
• Re: Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Albe Laurenz
• Re: suggestion: log_statement = sample
  • From: Bill Moran
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Rafael Martinez
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Marko Kreen
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Rafael Martinez
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Marko Kreen
• Re: Function does not exist
  • From: Andreas Wenk
• Re: Function does not exist
  • From: Pavel Stehule
• Re: Function does not exist
  • From: Andreas Wenk
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Rafael Martinez
• Re: Getting list of tables used within a query
  • From: Pavel Stehule
• Re: Concurrency issue under very heay loads
  • From: Bill Moran
• suggestion: log_statement = sample
  • From: Janning Vygen
• Re: Function does not exist
  • From: Pavel Stehule
• Re: Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Peter Eisentraut
• Re: best practice transitioning from one datatype to another
  • From: Arndt Lehmann
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: Allan Kamau
• Autovacuum and pg_stat_reset()
  • From: Rafael Martinez
• Re: Using the GEQO
  • From: Andres Freund
• Working around spurious unique constraint errors due to SERIALIZABLE bug
  • From: Florian Weimer
• Re: overwrite the encoding of a database
  • From: Andres Freund
• overwrite the encoding of a database
  • From: Massa, Harald Armin
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: Albe Laurenz
• Problems with 8.4, FLOAT8PASSBYVAL and x86_64 GNU/Linux
  • From: Rafael Martinez
• Getting list of tables used within a query
  • From: Marek Lewczuk
• Re: best practice transitioning from one datatype to another
  • From: Andreas Wenk
• Re: psql \du
  • From: Andreas Wenk
• Re: psql \du
  • From: Peter Eisentraut
• Re: initdb --encoding=LATIN1 fails on Windows
  • From: Abraham, Danny
• Re: How to DB export XML File in PostgreSQL?
  • From: Peter Eisentraut
• Re: initdb --locale=LATIN1 fails on Windows
  • From: Peter Eisentraut
• Using the GEQO
  • From: Ms swati chande
• Re: Function does not exist
  • From: dipesh mistry (Imap)
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: Scott Marlowe
• Re: How to DB export XML File in PostgreSQL?
  • From: Steve Choi
• Re: How to DB export XML File in PostgreSQL?
  • From: Thomas Kellerer
• How to DB export XML File in PostgreSQL?
  • From: Steve Choi
• Re: Concurrency issue under very heay loads
  • From: John R Pierce
• Re: Concurrency issue under very heay loads
  • From: Greenhorn
• Re: [PERFORM] Concurrency issue under very heay loads
  • From: ramasubramanian
• Concurrency issue under very heay loads
  • From: Raji Sridar (raji)
• Re: best practice transitioning from one datatype to another
  • From: Arndt Lehmann
• initdb --encoding=LATIN1 fails on Windows
  • From: Abraham, Danny
• psql \du
  • From: ANdreas Wenk
• Re: best practice transitioning from one datatype to another
  • From: Tom Lane
• Areca 1680 and RHEL/Centos 5.3 issue
  • From: Scott Marlowe
• Re: savepoints in 8.3.7 or whatever...
  • From: Scott Marlowe
• Re: initdb --locale=LATIN1 fails on Windows
  • From: Abraham, Danny
• Re: Function does not exist
  • From: Pavel Stehule
• Re: initdb --locale=LATIN1 fails on Windows
  • From: Abraham, Danny
• best practice transitioning from one datatype to another
  • From: CG
• Re: Function does not exist
  • From: ANdreas Wenk
• Re: change database
  • From: Bill Moran
• Re: PL/Python debugging - line numbers
  • From: Mike Toews
• Re: savepoints in 8.3.7 or whatever...
  • From: Alvaro Herrera
• Re: change database
  • From: Jeff Davis
• savepoints in 8.3.7 or whatever...
  • From: John R Pierce
• change database
  • From: Florian Chis
• Re: Automatic type conversion
  • From: Alvaro Herrera
• Function does not exist
  • From: dipesh mistry (Imap)
• Automatic type conversion
  • From: CG
• Re: initdb --locale=LATIN1 fails on Windows
  • From: Tom Lane
• Connection pool or load balancer supporting ident authentication
  • From: Stuart Bishop
• Re: filter duplicates by priority
  • From: Clark Slater
• initdb --locale=LATIN1 fails on Windows
  • From: Abraham, Danny
• Re: pg_stat_reset() not resetting all statistics counters
  • From: Brad Nicholson
• Re: pg_stat_reset() not resetting all statistics counters
  • From: Rafael Martinez
• Re: pg_stat_reset() not resetting all statistics counters
  • From: Rafael Martinez
• pg_stat_reset() not resetting all statistics counters
  • From: Rafael Martinez
• Re: problem with pg_restore?
  • From: Thomas Kellerer
• Re: cache lookup failed for function 72629
  • From: Lawrence Wong
• Re: problem with pg_restore?
  • From: Richard Huxton
• Re: problem with pg_restore?
  • From: David Wilson
• problem with pg_restore?
  • From: Jim Michaels
• Re: Custom Class variables
  • From: Alvaro Herrera
• PL/Python debugging - line numbers
  • From: Mike Toews
• Re: Request for features
  • From: David Fetter
• Custom Class variables
  • From: Michael Gould
• Re: [Q] single image Table across multiple PG servers
  • From: Kevin Kempter
• Re: [Q] single image Table across multiple PG servers
  • From: Scott Marlowe
• Re: [Q] single image Table across multiple PG servers
  • From: Greg Sabino Mullane
• Re: [Q] single image Table across multiple PG servers
  • From: Scott Mead
• Re: [Q] single image Table across multiple PG servers
  • From: Kevin Kempter
• Re: [Q] single image Table across multiple PG servers
  • From: Kevin Kempter
• Re: [Q] single image Table across multiple PG servers
  • From: V S P
• Re: filter duplicates by priority
  • From: Sam Mason
• Re: filter duplicates by priority
  • From: Martijn van Oosterhout
• Re: filter duplicates by priority
  • From: Tom Lane
• Re: filter duplicates by priority
  • From: Hartman, Matthew
• Re: prepared statements and DBD::Pg
  • From: Greg Sabino Mullane
• Re: pg_dump of a big table
  • From: Scott Mead
• Re: Best practices for moving UTF8 databases
  • From: Andres Freund
• Re: cache lookup failed for function 72629
  • From: Lawrence Wong
• Re: cache lookup failed for function 72629
  • From: Dean Rasheed
• Re: cache lookup failed for function 72629
  • From: Tom Lane
• Re: Checkpoint Tuning Question
  • From: Dan Armbrust
• filter duplicates by priority
  • From: Clark Slater
• Re: Best practices for moving UTF8 databases
  • From: Alvaro Herrera
• Re: Ascending / Descending Indexes
  • From: Alvaro Herrera
• Ascending / Descending Indexes
  • From: Michael Gould
• Re: cache lookup failed for function 72629
  • From: Lawrence Wong
• Re: cache lookup failed for function 72629
  • From: Merlin Moncure
• Re: Flexibility of views and functions?
  • From: Merlin Moncure
• Re: cache lookup failed for function 72629
  • From: Lawrence Wong
• Re: cache lookup failed for function 72629
  • From: Merlin Moncure
• cache lookup failed for function 72629
  • From: Lawrence Wong
• Connection pool/load balancer supporting ident authentication?
  • From: Stuart Bishop
• Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Marek Lewczuk
• Re: PostgreSQL-License
  • From: David Fetter
• Re: PostgreSQL-License
  • From: Peter Eisentraut
• Re: [Q] single image Table across multiple PG servers
  • From: Ransika de Silva
• PostgreSQL-License
  • From: Nenad Milasinovic
• Re: Request for features
  • From: Jasen Betts
• Re: [Q] single image Table across multiple PG servers
  • From: Scott Marlowe
• Re: Best practices for moving UTF8 databases
  • From: Andres Freund
• Re: Best practices for moving UTF8 databases
  • From: Jasen Betts
• Re: Checkpoint Tuning Question
  • From: Simon Riggs
• Re: How can I find out the space used on disk for a table/index
  • From: Craig Ringer
• [Q] single image Table across multiple PG servers
  • From: V S P
• Re: Start With... Connect By?
  • From: Scott Mead
• Re: Start With... Connect By?
  • From: Scott Mead
• Flexibility of views and functions?
  • From: Andreas
• Re: pg_migrator not setting values of sequences?
  • From: Bruce Momjian
• Re: large object does not exist after pg_migrator
  • From: Jamie Fox
• pg_migrator not setting values of sequences?
  • From: Tilmann Singer
• Re: Benetl, a free ETL tool for files using postgreSQL, is out in version 2.9
  • From: Michael Glaesemann
• large object does not exist after pg_migrator
  • From: Jamie Fox
• Benetl, a free ETL tool for files using postgreSQL, is out in version 2.9
  • From: benoît carpentier
• Re: Checkpoint Tuning Question
  • From: Dan Armbrust
• Re: Question]
  • From: Thomas Kellerer
• Re: Question]
  • From: Martie Krukkeland
• Re: UUID datatype question
  • From: Alvaro Herrera
• Re: UUID datatype question
  • From: David Kerr
• Re: pg_dump of a big table
  • From: Sam Mason
• Re: UUID datatype question
  • From: Tom Lane
• UUID datatype question
  • From: David Kerr
• pg_dump of a big table
  • From: Nelson Correia
• [no subject]
  • From: Jim Michaels
• Re: PostgreSQL 8.4 packages for Fedora 11?
  • From: Tim Landscheidt
• Re: uuid_hash declaration
  • From: Mel Flynn
• Re: PostgreSQL 8.4 packages for Fedora 11?
  • From: Tom Lane
• Re: Postgres 8.4 literal escaping
  • From: Alvaro Herrera
• Re: postgres/postgis indexes
  • From: Simon Riggs
• PostgreSQL 8.4 packages for Fedora 11?
  • From: Tim Landscheidt
• Re: Problem with Check Constraint in pg_restore
  • From: Alan Millington
• Re: uuid_hash declaration
  • From: Tom Lane
• Re: Postgres 8.4 literal escaping
  • From: Andreas
• Re: Question]
  • From: Raymond O'Donnell
• Re: Start With... Connect By?
  • From: Thomas Kellerer
• Re: Best practices for moving UTF8 databases
  • From: Andres Freund
• Re: uuid_hash declaration
  • From: Alvaro Herrera
• Re: Start With... Connect By?
  • From: David Fetter
• Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Marek Lewczuk
• Re: Problem with Check Constraint in pg_restore
  • From: Tom Lane
• Re: Request for features
  • From: Bruce Momjian
• Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Tom Lane
• Re: Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)
  • From: Chris Spotts
• Request for features
  • From: Michael Gould
• Rowsaffected return from NonExecQuery with stored procedure problem
  • From: DonnaR
• Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Marek Lewczuk
• Re: was field updated
  • From: Sim Zacks
• Re: ubuntu packages for 8.4
  • From: Leif B. Kristensen
• postgres/postgis indexes
  • From: Antonio Muñoz
• Re: Question
  • From: Jasen Betts
• Problem with Check Constraint in pg_restore
  • From: Alan Millington
• Re: ubuntu packages for 8.4
  • From: Jasen Betts
• Re: Start With... Connect By?
  • From: Pavel Stehule
• Re: Start With... Connect By?
  • From: Scott Marlowe
• Re: Start With... Connect By?
  • From: Pavel Stehule
• Re: uuid_hash declaration
  • From: Dimitri Fontaine
• Re: Rule acting as REPLACE INTO behave strange
  • From: IVO GELOV
• Re: Best practices for moving UTF8 databases
  • From: Albe Laurenz
• Re: Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)
  • From: Grzegorz Jaśkiewicz
• Re: Design question: Should "postgres" own all the db objects?
  • From: Albe Laurenz
• uuid_hash declaration
  • From: Mel Flynn
• PG binary images in bytea column
  • From: Johan Nel
• was field updated
  • From: Sim Zacks
• Re: Start With... Connect By?
  • From: Thomas Kellerer
• Start With... Connect By?
  • From: Philippe Lang
• Re: indexes on float8 vs integer
  • From: Dennis Gearon
• Re: How move a referenced table between schemas?
  • From: Tom Lane
• How move a referenced table between schemas?
  • From: Andreas
• Design question: Should "postgres" own all the db objects?
  • From: Andreas
• Re: how drop a role that owns stuff ?
  • From: Alvaro Herrera
• how drop a role that owns stuff ?
  • From: Andreas
• Re: How can I find out the space used on disk for a table/index
  • From: Greg Stark
• Re: Rule acting as REPLACE INTO behave strange
  • From: Tom Lane
• Re: indexes on float8 vs integer
  • From: Dennis Gearon
• Re: xpath() subquery for empty array
  • From: Roy Walter
• Re: xpath() subquery for empty array
  • From: Sam Mason
• Re: indexes on float8 vs integer
  • From: Brent Wood
• Re: xpath() subquery for empty array
  • From: Roy Walter
• Re: xpath() subquery for empty array
  • From: Scott Bailey
• Re: Postgresql databases as a web service
  • From: Scott Bailey
• Re: How can I find out the space used on disk for a table/index
  • From: Andres Freund
• Re: Postgresql databases as a web service
  • From: Scott Marlowe
• Could not Start Server (could not create any TCP/IP sockets)
  • From: Ms swati chande
• How can I find out the space used on disk for a table/index
  • From: Viktor Rosenfeld
• Rule acting as REPLACE INTO behave strange
  • From: IVO GELOV
• Re: Checkpoint Tuning Question
  • From: Simon Riggs
• Re: xpath() subquery for empty array
  • From: Sam Mason
• Re: xpath() subquery for empty array
  • From: Roy Walter
• Re: Checkpoint Tuning Question
  • From: Tom Lane
• Postgresql databases as a web service
  • From: dkeeney
• Re: Execute Immediate
  • From: Michael Gould
• Re: Checkpoint Tuning Question
  • From: Simon Riggs
• Re: xpath() subquery for empty array
  • From: Scott Bailey
• Re: [BUGS] BUG #4916: wish: more statistical functions (median, percentiles etc)
  • From: David Fetter
• Re: Execute Immediate
  • From: Pavel Stehule
• Execute Immediate
  • From: Michael Gould
• Re: INSERT only unique records
  • From: Sam Mason
• Best practices for moving UTF8 databases
  • From: Phoenix Kiula
• xpath() subquery for empty array
  • From: Roy Walter
• Re: Weird disk/table space consumption problem
  • From: Craig Ringer
• Re: INSERT only unique records
  • From: Craig Ringer
• Re: indexes on float8 vs integer
  • From: Scott Marlowe
• Re: Weird disk/table space consumption problem
  • From: Scott Marlowe
• Re: Weird disk/table space consumption problem
  • From: Scott Marlowe
• indexes on float8 vs integer
  • From: Dennis Gearon
• Re: Weird disk/table space consumption problem
  • From: Dirk Riehle
• Re: Weird disk/table space consumption problem
  • From: Dirk Riehle
• Re: [lapug] LAPUG Social - Tuesday Evening July 14
  • From: Aaron Glenn
• Re: Weird disk/table space consumption problem
  • From: Tom Lane
• Re: Weird disk/table space consumption problem
  • From: Scott Marlowe
• Weird disk/table space consumption problem
  • From: Dirk Riehle
• [no subject]
  • From: Dennis Gearon
• Re: XML import with DTD
  • From: Roy Walter
• LAPUG Social - Tuesday Evening July 14
  • From: Richard Broersma
• Anyone in New Zealand?
  • From: Josh Berkus
• Re: XML import with DTD
  • From: Tom Lane
• Re: Idle in transaction help
  • From: Martijn van Oosterhout
• Re: Using Postgres to store genetic data
  • From: Martin Gainty
• Re: Question
  • From: Raymond O'Donnell
• INSERT only unique records
  • From: Mark Felegyhazi
• Question
  • From: Jorge Arangoitia Fernandez Baca
• Re: Postgres 8.4 literal escaping
  • From: Niederland
• Re: How to trace client sql requests?
  • From: Alban Hertroys
• Re: Best practices to WorkFlow design?
  • From: Alban Hertroys
• Re: XML import with DTD
  • From: Roy Walter
• Date Time Arithmetic Speed
  • From: Dennis Gearon
• Re: Using Postgres to store genetic data
  • From: Peter Hunsberger
• [no subject]
  • From: Clark Slater
• Re: Idle in transaction help
  • From: Scot Kreienkamp
• Re: singletons per row in table AND locking response
  • From: Sam Mason
• Re: [Fwd: Re: How to trace client sql requests?]
  • From: Erik Jones
• Re: change location of postmaster.pid file?
  • From: Janet Jacobsen
• Re: Idle in transaction help
  • From: Erik Jones
• Re: Idle in transaction help
  • From: Scott Marlowe
• Re: BR/
  • From: James B. Byrne
• Re: BR/
  • From: Scott Marlowe
• Re: BR/
  • From: James B. Byrne
• Re: change location of postmaster.pid file?
  • From: John R Pierce
• Re: BR/
  • From: Scott Marlowe
• Re: change location of postmaster.pid file?
  • From: Greg Stark
• Re: change location of postmaster.pid file?
  • From: Tom Lane
• Re: Idle in transaction help
  • From: Scot Kreienkamp
• Re: Idle in transaction help
  • From: Scott Marlowe
• change location of postmaster.pid file?
  • From: Janet Jacobsen
• Re: BR/
  • From: Alvaro Herrera
• Re: psql language
  • From: Stuart McGraw
• Re: Idle in transaction help
  • From: John R Pierce
• Re: is autovacuum recommended?
  • From: Scott Marlowe
• Re: Using Postgres to store genetic data
  • From: Steve Crawford
• Re: is autovacuum recommended?
  • From: Willy-Bas Loos
• Re: Inserted data is disappearing
  • From: James B. Byrne
• Re: Idle in transaction help
  • From: Scot Kreienkamp
• [Fwd: Re: How to trace client sql requests?]
  • From: James B. Byrne
• Re: Idle in transaction help
  • From: John R Pierce
• Re: Inserted data is disappearing
  • From: Bill Moran
• BR/
  • From: James B. Byrne
• Using Postgres to store genetic data
  • From: Peter Hunsberger
• Re: How to trace client sql requests?
  • From: hubert depesz lubaczewski
• Idle in transaction help
  • From: Scot Kreienkamp
• Re: How to trace client sql requests?
  • From: James B. Byrne
• Re: Checkpoint Tuning Question
  • From: Dan Armbrust
• Re: How to trace client sql requests?
  • From: hubert depesz lubaczewski
• Re: Overhead of union versus union all
  • From: Jeff Davis
• Re: Overhead of union versus union all
  • From: Scott Marlowe
• Re: XML import with DTD
  • From: artacus
• Re: Overhead of union versus union all
  • From: Greg Stark
• How to trace client sql requests?
  • From: James B. Byrne
• Re: REINDEX "is not a btree"
  • From: decibel
• Re: Overhead of union versus union all
  • From: Jeff Davis
• Re: SELECT DISTINCT very slow
  • From: Jeff Davis
• Re: UNION question
  • From: Brandon Metcalf
• Re: UNION question
  • From: Brandon Metcalf
• Re: UNION question
  • From: Tom Lane
• Re: UNION question
  • From: Hartman, Matthew
• Re: UNION question
  • From: Hartman, Matthew
• UNION question
  • From: Brandon Metcalf
• Re: Checkpoint Tuning Question
  • From: Tom Lane
• Re: Checkpoint Tuning Question
  • From: Simon Riggs
• Re: REINDEX "is not a btree"
  • From: Alan Hodgson
• Re: REINDEX "is not a btree"
  • From: Tom Lane
• Re: SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Tom Lane
• XML import with DTD
  • From: Roy Walter
• SPI_ERROR_CONNECT within pl/pgsql, PG 8.4
  • From: Marek Lewczuk
• Re: REINDEX "is not a btree"
  • From: Vanessa Lopez
• Re: Database storage
  • From: Scott Marlowe
• Re: Database storage
  • From: Bill Moran
• Re: Database storage
  • From: John R Pierce
• Re: Database storage
  • From: nabble . 30 . miller_2555
• Re: Checkpoint Tuning Question
  • From: Tom Lane
• Re: psql language
  • From: Hiroshi Saito
• Re: Overhead of union versus union all
  • From: Simon Riggs
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: Overhead of union versus union all
  • From: Simon Riggs
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: Overhead of union versus union all
  • From: Simon Riggs
• Re: PostgreSQL and Poker
  • From: Jasen Betts
• Best practices to WorkFlow design?
  • From: Andre Lopes
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: SELECT DISTINCT very slow
  • From: Greg Stark
• Re: SELECT DISTINCT very slow
  • From: Ben Harper
• Re: ubuntu packages for 8.4
  • From: Tim Uckun
• Re: Checkpoint Tuning Question
  • From: Simon Riggs
• Re: ubuntu packages for 8.4
  • From: Stuart Bishop
• Re: Overhead of union versus union all
  • From: Simon Riggs
• Re: Performance problem with low correlation data
  • From: m_lists
• Re: REINDEX "is not a btree"
  • From: decibel
• Re: cache reads vs. disk reads
  • From: decibel
• Re: Multi - table statistics
  • From: decibel
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: Overhead of union versus union all
  • From: Scott Marlowe
• Re: ubuntu packages for 8.4
  • From: Scott Bailey
• psql language
  • From: Stuart McGraw
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: Overhead of union versus union all
  • From: Scott Bailey
• Re: ubuntu packages for 8.4
  • From: Bret Fledderjohn
• Re: Database storage
  • From: Scott Marlowe
• Re: Database storage
  • From: Greg Stark
• ubuntu packages for 8.4
  • From: Tim Uckun
• Re: pg_dump PostgreSQL 8.4
  • From: serafin segador
• Re: SELECT DISTINCT very slow
  • From: Tom Lane
• Re: SELECT DISTINCT very slow
  • From: Greg Stark
• Re: Database storage
  • From: Scott Marlowe
• Database storage
  • From: nabble . 30 . miller_2555
• Re: Postgres 8.4 literal escaping
  • From: Tom Lane
• Re: Help me please...
  • From: John R Pierce
• Re: Help me please...
  • From: jacob
• Re: Help me please...
  • From: jacob
• Re: Overhead of union versus union all
  • From: Bruce Momjian
• Re: Overhead of union versus union all
  • From: Adam Rich