Postgresql General Discussion

• Thread Index

• Public and Grants
  • From: Michael Gould
• Re: Date with time zone
  • From: Adrian Klaver
• Re: return value for PQbinaryTuples
  • From: Merlin Moncure
• Re: Strange "bug" in dump ?
  • From: Tom Lane
• Re: Cannot allocate memory for output buffer
  • From: Martijn van Oosterhout
• postgres log file mode
  • From: Filip Rembiałkowski
• Re: Postgres security article
  • From: John Meyer
• Re: Postgres security article
  • From: Jean-Yves F. Barbier
• Postgres security article
  • From: Colin Streicher
• Re: Locale query
  • From: Roger Leigh
• Re: Strange "bug" in dump ?
  • From: Denis BUCHER
• Re: Strange "bug" in dump ?
  • From: Rikard Bosnjakovic
• Strange "bug" in dump ?
  • From: Denis BUCHER
• Date with time zone
  • From: Eduardo Piombino
• Re: Locale query
  • From: admin@xxxxxxxxxxxxxxxx
• Re: Postgresql8.4 install breaks Evolution on Ubuntu 9.10
  • From: Magnus Hagander
• Re: Postgresql8.4 install breaks Evolution on Ubuntu 9.10
  • From: Sachin Srivastava
• Locale query
  • From: admin@xxxxxxxxxxxxxxxx
• Postgresql8.4 install breaks Evolution on Ubuntu 9.10
  • From: Leonardo Camargo
• Re: Access a Field / Column of a resultset by Number
  • From: Scott Marlowe
• Re: incorrect restore from pg_dumpall
  • From: Paul Ramsey
• incorrect restore from pg_dumpall
  • From: Tomas Lanczos
• return value for PQbinaryTuples
  • From: bbhe
• Access a Field / Column of a resultset by Number
  • From: Daniel Schuchardt
• Re: Mysql migration to Postgresql
  • From: Cjkalbente
• Re: Access a Field / Column of a resultset by Number
  • From: Daniel Schuchardt
• Re: Cannot allocate memory for output buffer
  • From: Tom Lane
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Tom Lane
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Stephan Szabo
• Re: vacuumdb -z do a reindex?
  • From: Scott Marlowe
• Re: Cannot allocate memory for output buffer
  • From: Peter Erickson
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Guillaume Lelarge
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Jeff Amiel
• Re: vacuumdb -z do a reindex?
  • From: Guillaume Lelarge
• vacuumdb -z do a reindex?
  • From: Irene Barg
• Re: Cannot allocate memory for output buffer
  • From: Tom Lane
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Tom Lane
• Cannot allocate memory for output buffer
  • From: Pete Erickson
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Jeff Amiel
• Re: empty string causes planner to avoid index. Makes me sad.
  • From: Tom Lane
• empty string causes planner to avoid index. Makes me sad.
  • From: Jeff Amiel
• Re: READ ONLY & I/O ERROR
  • From: Scott Marlowe
• Re: date_trunct() and start of week
  • From: Tom Lane
• Re: Invalid redo in checkpoint record
  • From: Shakil Shaikh
• Re: pg_standby instructions
  • From: Rikard Bosnjakovic
• Re: pg_standby instructions
  • From: akp geek
• Re: Storing images in database for web applications
  • From: Massa, Harald Armin
• Re: Storing images in database for web applications
  • From: Craig Ringer
• Re: Bestpractice for upgrading from enterpriseDB 8.3.3 to rpm 8.4.1.
  • From: Richard Huxton
• Re: Is there any reason why databases cannot have a binary formatted datatype?
  • From: Richard Huxton
• Re: date_trunct() and start of week
  • From: Alban Hertroys
• Storing images in database for web applications
  • From: Thom Brown
• Re: Is there any reason why databases cannot have a binary formatted datatype?
  • From: John R Pierce
• Re: date_trunct() and start of week
  • From: Thomas Kellerer
• Is there any reason why databases cannot have a binary formatted datatype?
  • From: Andrew Maclean
• Re: date_trunct() and start of week
  • From: Thomas Markus
• return value for PQbinaryTuples
  • From: bbhe
• Re: date_trunct() and start of week
  • From: Thomas Kellerer
• Re: date_trunct() and start of week
  • From: Rikard Bosnjakovic
• Re: date_trunct() and start of week
  • From: Thomas Kellerer
• Re: Invalid redo in checkpoint record
  • From: Craig Ringer
• Re: transparently log a right error
  • From: Craig Ringer
• Re: date_trunct() and start of week
  • From: Thom Brown
• Re: date_trunct() and start of week
  • From: Thom Brown
• Re: date_trunct() and start of week
  • From: Adrian Klaver
• date_trunct() and start of week
  • From: Thomas Kellerer
• Re: How use input parameter as path to COPY in function?
  • From: Bill Todd
• Re: READ ONLY & I/O ERROR
  • From: Scott Marlowe
• Re: Invalid redo in checkpoint record
  • From: Scott Marlowe
• Invalid redo in checkpoint record
  • From: Shak
• Re: How are blobs (oid) stored?
  • From: Jérôme Etévé
• transparently log a right error
  • From: Jean-Yves F. Barbier
• Re: How are blobs (oid) stored?
  • From: Tom Lane
• Re: READ ONLY & I/O ERROR
  • From: Alan Hodgson
• Re: specifying a password on the cmd line for db connect
  • From: Tom Lane
• Bestpractice for upgrading from enterpriseDB 8.3.3 to rpm 8.4.1.
  • From: Chris Barnes
• Re: READ ONLY & I/O ERROR
  • From: Grzegorz Jaśkiewicz
• Re: READ ONLY & I/O ERROR
  • From: Grzegorz Jaśkiewicz
• Re: Error on VACCUM ANALYZE
  • From: Sam Jas
• Re: READ ONLY & I/O ERROR
  • From: Sam Jas
• Re: READ ONLY & I/O ERROR
  • From: Grzegorz Jaśkiewicz
• READ ONLY & I/O ERROR
  • From: Sam Jas
• Re: Wiki page on vacuum full
  • From: Jérôme Etévé
• How are blobs (oid) stored?
  • From: Jérôme Etévé
• Error on VACCUM ANALYZE
  • From: A.Bhattacharya
• Re: specifying a password on the cmd line for db connect
  • From: Jasen Betts
• Re: specifying a password on the cmd line for db connect
  • From: Jasen Betts
• Re: Wiki page on vacuum full
  • From: Craig Ringer
• Re: limiting resources to users
  • From: Craig Ringer
• Re: limiting resources to users
  • From: Gauthier, Dave
• Wiki page on vacuum full
  • From: Craig Ringer
• Re: How use input parameter as path to COPY in function?
  • From: Tom Lane
• How use input parameter as path to COPY in function?
  • From: Bill Todd
• Re: limiting resources to users
  • From: Craig Ringer
• Re: Mysql migration to Postgresql
  • From: Craig Ringer
• Re: Mysql migration to Postgresql
  • From: Filip Rembiałkowski
• Re: limiting resources to users
  • From: Craig Ringer
• Re: Getting "duplicate key value violates unique constraint" on 2nd run of function.
  • From: David Kerr
• Re: Postgres database performance on 6 core Opteron vs 4 core Xeon
  • From: Scott Marlowe
• Re: Getting "duplicate key value violates unique constraint" on 2nd run of function.
  • From: Scott Marlowe
• Re: pg_standby instructions
  • From: Devrim GÜNDÜZ
• Re: Data Warehousing
  • From: melina386
• Mysql migration to Postgresql
  • From: mrciken
• Re: Re: I need help creating a composite type with some sort of constraints.
  • From: John Oyler
• PostgreSQL RPM packages for Fedora-12 released
  • From: Devrim GÜNDÜZ
• Re: pg_standby instructions
  • From: Joshua D. Drake
• Re: pg_standby instructions
  • From: akp geek
• Getting "duplicate key value violates unique constraint" on 2nd run of function.
  • From: David Kerr
• Re: limiting resources to users
  • From: Bruno Lavoie
• Postgres database performance on 6 core Opteron vs 4 core Xeon
  • From: Postgres User
• Re: pgsql 'prefix'
  • From: Dimitri Fontaine
• Re: limiting resources to users
  • From: Jean-Yves F. Barbier
• Re: Re: I need help creating a composite type with some sort of constraints.
  • From: Merlin Moncure
• Re: change of oid values?
  • From: Thom Brown
• Re: limiting resources to users
  • From: Bill Moran
• change of oid values?
  • From: Yadira Lizama Mue
• Re: limiting resources to users
  • From: Jean-Yves F. Barbier
• Postgres database performance on 6 core Opteron vs 4 core Xeon
  • From: Postgres User
• Re: limiting resources to users
  • From: John R Pierce
• limiting resources to users
  • From: Gauthier, Dave
• Re: pgsql 'prefix' error
  • From: Harald Fuchs
• Re: [BUGS] Re: How duplicate data produce when a UNIQUE index exite ?
  • From: Greg Smith
• Re: pgsql 'prefix' error
  • From: Dimitri Fontaine
• Re: [BUGS] Re: How duplicate data produce when a UNIQUE index exite ?
  • From: Tom Lane
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Alexandra Roy
• 答复: [GENERAL] How duplicate data produce when a UNIQUE index exite ?
  • From: RD黄永卫
• Re: Re: I need help creating a composite type with some sort of constraints.
  • From: John Oyler
• Re: Excluding null return values from functions
  • From: Pavel Stehule
• Excluding null return values from functions
  • From: Jason Armstrong
• Re: [PERFORM] Strange performance degradation
  • From: Matthew Wakeling
• Re: How duplicate data produce when a UNIQUE index exite ?
  • From: Greg Smith
• Re: 答复: [GENERAL] How duplicate data produce when a UNIQUE index exite ?
  • From: Scott Marlowe
• Re: How duplicate data produce when a UNIQUE index exite ?
  • From: Scott Marlowe
• How duplicate data produce when a UNIQUE index exite ?
  • From: RD黄永卫
• Re: pgsql 'prefix' error
  • From: Bino Oetomo
• Re: Re: I need help creating a composite type with some sort of constraints.
  • From: John Oyler
• Re: howto escape my string
  • From: Jean-Yves F. Barbier
• Re: Processing Delay
  • From: Sam Jas
• Re: howto escape my string
  • From: Brian Modra
• Re: which software to replicate a database on windows xp/vista is the best???
  • From: Greg Smith
• Re: pg_attribute.attnum - wrong column ordinal?
  • From: Konstantin Izmailov
• Re: pg_attribute.attnum - wrong column ordinal?
  • From: Greg Stark
• Re: Processing Delay
  • From: Scott Marlowe
• Re: pg_attribute.attnum - wrong column ordinal?
  • From: Konstantin Izmailov
• Re: pg_attribute.attnum - wrong column ordinal?
  • From: Greg Stark
• Re: Processing Delay
  • From: Christophe Pettus
• pg_attribute.attnum - wrong column ordinal?
  • From: Konstantin Izmailov
• Processing Delay
  • From: Michael Lawson (mshindo)
• Re: [PERFORM] Strange performance degradation
  • From: Denis Lussier
• Re: Re: I need help creating a composite type with some sort of constraints.
  • From: Merlin Moncure
• Re: Partitioning table and dynamic SQL in trigger
  • From: silly8888
• Re: exclude table from transactions
  • From: Tom Lane
• Re: exclude table from transactions
  • From: Christophe Pettus
• Re: I need help creating a composite type with some sort of constraints.
  • From: John Oyler
• exclude table from transactions
  • From: Kurt
• Re: [PERFORM] Strange performance degradation
  • From: Denis Lussier
• which software to replicate a database on windows xp/vista is the best???
  • From: erobles
• howto escape my string
  • From: Jean-Yves F. Barbier
• Re: [PERFORM] Strange performance degradation
  • From: Ing. Marcos Ortiz Valmaseda
• Re: [HACKERS] Updating column on row update
  • From: Robert Haas
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [COMMITTERS] recover deleted records
  • From: Scott Bailey
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Kevin Grittner
• Re: [HACKERS] Updating column on row update
  • From: Scott Marlowe
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Robert Haas
• Re: [HACKERS] Updating column on row update
  • From: Kevin Grittner
• Re: pgsql 'prefix' error
  • From: Harald Fuchs
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Kevin Grittner
• Re: Client Encoding and Latin characters
  • From: Lee Hachadoorian
• Re: ora2pg and DBD::Pg
  • From: Andrej
• Re: Client Encoding and Latin characters
  • From: Tom Lane
• Client Encoding and Latin characters
  • From: Lee Hachadoorian
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Albe Laurenz
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Alexandra Roy
• Re: [PERFORM] Strange performance degradation
  • From: Matthew Wakeling
• Re: [PERFORM] Strange performance degradation
  • From: Lorenzo Allegrucci
• Re: [BUGS] BUG #5211: invalid password
  • From: David Fetter
• Partitioning table and dynamic SQL in trigger
  • From: Michal Szymanski
• Re: [COMMITTERS] recover deleted records
  • From: Pavel Stehule
• Re: Multicolumn index including tsvector.
  • From: Alban Hertroys
• Re: [PERFORM] Strange performance degradation
  • From: Matthew Wakeling
• Re: [COMMITTERS] recover deleted records
  • From: Allan Morris Caras
• Re: [HACKERS] Updating column on row update
  • From: Hannu Krosing
• pgsql 'prefix' error
  • From: Bino Oetomo
• Re: [COMMITTERS] recover deleted records
  • From: Pavel Stehule
• Re: [COMMITTERS] recover deleted records
  • From: Allan Morris Caras
• Re: [COMMITTERS] recover deleted records
  • From: Pavel Stehule
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Albe Laurenz
• Re: get a log of queries that take up a lot of CPU or take a very long time.
  • From: Sam Jas
• Re: How is the right query for this condition ?
  • From: Bino Oetomo
• Re: Strange performance degradation
  • From: Sam Jas
• Re: [HACKERS] Updating column on row update
  • From: Thom Brown
• Re: [HACKERS] Updating column on row update
  • From: Hannu Krosing
• How identify a long running transaction
  • From: Bill Todd
• Re: [HACKERS] Updating column on row update
  • From: Craig Ringer
• Re: Multicolumn index including tsvector.
  • From: Kris Gale
• Re: Multicolumn index including tsvector.
  • From: Tom Lane
• Multicolumn index including tsvector.
  • From: Kris Gale
• Re: I need help creating a composite type with some sort of constraints.
  • From: Scott Bailey
• Re: get a log of queries that take up a lot of CPU or take a very long time.
  • From: Alan Hodgson
• get a log of queries that take up a lot of CPU or take a very long time.
  • From: Tim Uckun
• Re: C++ and Postgis
  • From: Martin Gainty
• Re: C++ and Postgis
  • From: John R Pierce
• I need help creating a composite type with some sort of constraints.
  • From: John Oyler
• Re: Strange performance degradation
  • From: Tom Lane
• C++ and Postgis
  • From: Pedro Doria Meunier
• Re: obtaining ARRAY position for a given match
  • From: Pedro Doria Meunier
• Re: Strange performance degradation
  • From: Bill Moran
• Re: Strange performance degradation
  • From: Lorenzo Allegrucci
• Re: PG_STANDBY ISSUE
  • From: Greg Smith
• Re: PG_STANDBY ISSUE
  • From: akp geek
• Re: [HACKERS] Updating column on row update
  • From: Andrew Gierth
• Re: PG_STANDBY ISSUE
  • From: Richard Huxton
• Re: Error in Loading DLL using Postgres function
  • From: Merlin Moncure
• Re: Comprehensive operator list
  • From: Thom Brown
• Re: Comprehensive operator list
  • From: Merlin Moncure
• Fwd: PG_STANDBY ISSUE
  • From: akp geek
• Comprehensive operator list
  • From: Thom Brown
• Re: How is the right query for this condition ?
  • From: Harald Fuchs
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Andrew Dunstan
• Re: [HACKERS] Updating column on row update
  • From: Andrew Gierth
• Re: [HACKERS] Updating column on row update
  • From: Thom Brown
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Robert Haas
• Error in Loading DLL using Postgres function
  • From: A.Bhattacharya
• Re: Backup Postgre server
  • From: AnthonyV
• Re: Backup Postgre server
  • From: Filip Rembiałkowski
• Re: Backup Postgre server
  • From: David Fetter
• Backup Postgre server
  • From: AnthonyV
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Alexandra Roy
• Re: [HACKERS] Updating column on row update
  • From: Thom Brown
• Re: ora2pg and DBD::Pg
  • From: Alexandra Roy
• Re: Returning bigint from C extension
  • From: Martijn van Oosterhout
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Alexandra Roy
• Returning bigint from C extension
  • From: Jason Armstrong
• Re: Is there a tool used to display statement times from postgres logs
  • From: Pinter Bernd
• Re: [HACKERS] Updating column on row update
  • From: Scott Marlowe
• Re: [HACKERS] Updating column on row update
  • From: Craig Ringer
• Re: [HACKERS] Updating column on row update
  • From: Scott Marlowe
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Andrew Dunstan
• Re: How is the right query for this condition ?
  • From: Bino Oetomo
• Re: [HACKERS] Updating column on row update
  • From: Tom Lane
• Re: [HACKERS] Updating column on row update
  • From: Robert Haas
• Re: How is the right query for this condition ?
  • From: Brian Modra
• Re: error linking with PostgreSQL
  • From: Tom Lane
• How is the right query for this condition ?
  • From: Bino Oetomo
• How to link with postgresql in gcc?
  • From: Daniel
• error linking with PostgreSQL
  • From: Daniel
• Re: How to link with postgresql in gcc?
  • From: Daniel
• Re: ERROR: aggregate function calls cannot be nested
  • From: Tom Lane
• Re: Updating column on row update
  • From: silly8888
• ERROR: aggregate function calls cannot be nested
  • From: Jonathan Blitz
• Re: Updating column on row update
  • From: Tom Lane
• Re: Updating column on row update
  • From: Thom Brown
• Re: Updating column on row update
  • From: Craig Ringer
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: Planning problem: pushing conditions through GROUP BY
  • From: Martijn van Oosterhout
• Re: Updating column on row update
  • From: Thom Brown
• Re: Updating column on row update
  • From: Christophe Pettus
• Re: Updating column on row update
  • From: Adrian Klaver
• Re: Updating column on row update
  • From: Thom Brown
• Re: Updating column on row update
  • From: Scott Marlowe
• Re: Updating column on row update
  • From: Scott Marlowe
• Re: Updating column on row update
  • From: Thom Brown
• Re: Updating column on row update
  • From: Adrian Klaver
• Re: Updating column on row update
  • From: Scott Marlowe
• Re: Updating column on row update
  • From: Aaron Burnett
• Re: Updating column on row update
  • From: Thom Brown
• Updating column on row update
  • From: Thom Brown
• Re: Planning problem: pushing conditions through GROUP BY
  • From: Tom Lane
• Re: Books, the lulu.com scam
  • From: Thom Brown
• Re: Books, the lulu.com scam
  • From: Ivano Luberti
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: How to get RTREE performance from GIST index?
  • From: Martijn van Oosterhout
• Re: How well clustered is a table?
  • From: A. Kretschmer
• How well clustered is a table?
  • From: Jonathan Blitz
• Re: How to get RTREE performance from GIST index?
  • From: Alban Hertroys
• Re: How to get RTREE performance from GIST index?
  • From: Alban Hertroys
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: How to get RTREE performance from GIST index?
  • From: Martijn van Oosterhout
• Planning problem: pushing conditions through GROUP BY
  • From: Martijn van Oosterhout
• Re: How to get RTREE performance from GIST index?
  • From: Alban Hertroys
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: How to get RTREE performance from GIST index?
  • From: Alban Hertroys
• Re: How to get RTREE performance from GIST index?
  • From: Thom Brown
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: How to get RTREE performance from GIST index?
  • From: Martijn van Oosterhout
• Re: How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: Books, the lulu.com scam
  • From: Dave Coventry
• Re: How to get RTREE performance from GIST index?
  • From: Tom Lane
• Re: Books, the lulu.com scam
  • From: Rikard Bosnjakovic
• Re: How to get RTREE performance from GIST index?
  • From: Thom Brown
• How to get RTREE performance from GIST index?
  • From: Clive Page
• Re: ERROR: (custom type via CREATE TYPE) is not a valid base type for a domain
  • From: John Oyler
• How to get RTREE performance from GIST indexing?
  • From: Clive Page
• Re: ERROR: (custom type via CREATE TYPE) is not a valid base type for a domain
  • From: Tom Lane
• Re: Books, the lulu.com scam
  • From: Tim Landscheidt
• ERROR: (custom type via CREATE TYPE) is not a valid base type for a domain
  • From: John Oyler
• Re: Books, the lulu.com scam
  • From: Yordan Radunchev
• Re: Books, the lulu.com scam
  • From: doug livesey
• Re: Books, the lulu.com scam
  • From: Bill Todd
• Re: Books, the lulu.com scam
  • From: Thom Brown
• Re: Books, the lulu.com scam
  • From: Alan Gruskoff
• Re: Is there a tool used to display statement times from postgres logs
  • From: Ben Chobot
• use log_statement to log only SELECTs?
  • From: Brian Witt
• Re: panic failed to add item
  • From: Scott Marlowe
• Re: panic failed to add item
  • From: Tom Lane
• Re: panic failed to add item
  • From: Scott Marlowe
• Re: panic failed to add item
  • From: Tom Lane
• Re: panic failed to add item
  • From: Scott Marlowe
• Re: panic failed to add item
  • From: Tom Lane
• PG_STANDBY ISSUE
  • From: akp geek
• Re: Strange performance degradation
  • From: Lorenzo Allegrucci
• Re: Strange performance degradation
  • From: Lorenzo Allegrucci
• panic failed to add item
  • From: Scott Marlowe
• Re: ora2pg and DBD::Pg
  • From: Stephen Frost
• Re: checkpoints/bgwriter tuning verification
  • From: Andres Freund
• Re: Easier to use warm standby in 8.4?
  • From: Greg Smith
• Re: Is there a tool used to display statement times from postgres logs
  • From: Chris Barnes
• Re: Books
  • From: Joshua D. Drake
• Re: PLPerl - Undefined symbol "MemoryContextSwitchTo"
  • From: Doug Sampson
• Easier to use warm standby in 8.4?
  • From: Erik Jones
• Re: Is there a tool used to display statement times from postgres logs
  • From: Joshua D. Drake
• Re: Is there a tool used to display statement times from postgres logs
  • From: Bill Moran
• Re: Is there a tool used to display statement times from postgres logs
  • From: Thom Brown
• Re: Is there a tool used to display statement times from postgres logs
  • From: Chris Barnes
• Re: DBD::Pg 2.15.1 compilation failed
  • From: Greg Sabino Mullane
• Re: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876
  • From: Matt Solnit
• Re: Is there a tool used to display statement times from postgres logs
  • From: John R Pierce
• Is there a tool used to display statement times from postgres logs
  • From: Chris Barnes
• Re: stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876
  • From: Merlin Moncure
• Re: ora2pg and DBD::Pg
  • From: Joshua D. Drake
• Re: pg_standby instructions
  • From: Joshua D. Drake
• stuck spinlock (0x2aac3678b0e0) detected at dynahash.c:876
  • From: Matt Solnit
• Re: pg_standby instructions
  • From: akp geek
• ora2pg and DBD::Pg
  • From: Alexandra Roy
• DBD::Pg 2.15.1 compilation failed
  • From: Alexandra Roy
• Re: Allowing for longer table names (>64 characters)
  • From: Bret
• Re: PLPerl - Undefined symbol "MemoryContextSwitchTo"
  • From: Doug Sampson
• Re: PLPerl - Undefined symbol "MemoryContextSwitchTo"
  • From: Tom Lane
• PLPerl - Undefined symbol "MemoryContextSwitchTo"
  • From: Doug Sampson
• Re: [PERFORM] Strange performance degradation
  • From: Matthew Wakeling
• Re: how to use a cursor for update?
  • From: Tom Lane
• Re: index storage planning
  • From: Ray Stell
• Re: Strange performance degradation
  • From: Tom Lane
• Re: Strange performance degradation
  • From: Brian Modra
• Re: using window-functions to get freshest value - how?
  • From: Massa, Harald Armin
• Re: using window-functions to get freshest value - how?
  • From: Thom Brown
• Re: using window-functions to get freshest value - how?
  • From: silly8888
• Re: Strange performance degradation
  • From: Sam Jas
• Re: using window-functions to get freshest value - how?
  • From: A. Kretschmer
• Re: using window-functions to get freshest value - how?
  • From: Thom Brown
• Re: using window-functions to get freshest value - how?
  • From: Massa, Harald Armin
• Re: using window-functions to get freshest value - how?
  • From: A. Kretschmer
• Re: using window-functions to get freshest value - how?
  • From: Thomas Kellerer
• Re: using window-functions to get freshest value - how?
  • From: hubert depesz lubaczewski
• Re: using window-functions to get freshest value - how?
  • From: silly8888
• Re: using window-functions to get freshest value - how?
  • From: silly8888
• Re: using window-functions to get freshest value - how?
  • From: Massa, Harald Armin
• Re: using window-functions to get freshest value - how?
  • From: Thomas Kellerer
• Re: Allowing for longer table names (>64 characters)
  • From: Tino Wildenhain
• using window-functions to get freshest value - how?
  • From: Massa, Harald Armin
• Re: Allowing for longer table names (>64 characters)
  • From: A. Kretschmer
• Strange performance degradation
  • From: Lorenzo Allegrucci
• how to use a cursor for update?
  • From: nicola zandonà
• Re: Allowing for longer table names (>64 characters)
  • From: Allan Kamau
• Re: Allowing for longer table names (>64 characters)
  • From: A. Kretschmer
• Allowing for longer table names (>64 characters)
  • From: Allan Kamau
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: Tom Lane
• Re: Dblink to Oracle
  • From: Sam Jas
• Re: Possible bug with array_agg
  • From: Pavel Stehule
• pgbouncer connections used
  • From: Scott Ribe
• HA-JDBC
  • From: David Kerr
• Re: DB terminating [on Windows]
  • From: Magnus Hagander
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: araza
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: Devrim GÜNDÜZ
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: araza
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: araza
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: Devrim GÜNDÜZ
• Re: Books
  • From: Greg Smith
• Re: Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Raimon Fernandez
• Re: Books
  • From: Chris Browne
• Re: Possible bug with array_agg
  • From: Scott Bailey
• Re: Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: Joshua D. Drake
• Re: Possible bug with array_agg
  • From: Guillaume Lelarge
• Re: Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Kovalevski Andrei
• Issues with Redhat 4 Postgresql 8.4 and support of libxml
  • From: araza
• Re: Possible bug with array_agg
  • From: Scott Bailey
• Re: Possible bug with array_agg
  • From: Tom Lane
• Re: Possible bug with array_agg
  • From: Pavel Stehule
• Re: obtaining ARRAY position for a given match
  • From: Pavel Stehule
• Re: obtaining ARRAY position for a given match
  • From: Sam Mason
• Possible bug with array_agg
  • From: Scott Bailey
• Re: obtaining ARRAY position for a given match
  • From: Scott Bailey
• Re: obtaining ARRAY position for a given match
  • From: Pavel Stehule
• Re: obtaining ARRAY position for a given match
  • From: Sam Mason
• Re: Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Raimon Fernandez
• Re: obtaining ARRAY position for a given match
  • From: Scott Bailey
• Re: obtaining ARRAY position for a given match
  • From: Sam Mason
• Re: obtaining ARRAY position for a given match
  • From: Scott Bailey
• Re: obtaining ARRAY position for a given match
  • From: Merlin Moncure
• Re: obtaining ARRAY position for a given match
  • From: Scott Bailey
• Re: Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Raimon Fernandez
• Re: obtaining ARRAY position for a given match
  • From: Sam Mason
• Re: Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Kovalevski Andrei
• Re: obtaining ARRAY position for a given match
  • From: Pavel Stehule
• Encoding using the Frontend/Backend Protocol TCP/IP
  • From: Raimon Fernandez
• Re: obtaining ARRAY position for a given match
  • From: Scott Bailey
• Books
  • From: Thomas Løcke
• index storage planning
  • From: Ray Stell
• Re: Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Tom Lane
• Re: Dblink to Oracle
  • From: Bruno Lavoie
• Re: Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Thom Brown
• Dblink to Oracle
  • From: Nicola Farina
• Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Tech 2010
• Re: Enum on-disk format
  • From: Peter Eisentraut
• obtaining ARRAY position for a given match
  • From: Pedro Doria Meunier
• text search query planning
  • From: Henk van Lingen
• Re: Can anyone help setting up pgbouncer?
  • From: Richard Huxton
• Re: Can anyone help setting up pgbouncer?
  • From: Nick
• Re: Enum on-disk format
  • From: Scott Bailey
• Information of streaming about PostgreSQL Conference 2009 Japan
  • From: Kaori Inaba
• Re: DB terminating
  • From: Craig Ringer
• Re: Customize the install directory of the postgres DB
  • From: weixiang tam
• Re: Enum on-disk format
  • From: Tom Lane
• Enum on-disk format
  • From: Scott Bailey
• Re: Can anyone help setting up pgbouncer?
  • From: Richard Huxton
• Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Tech 2010
• Re: [Fwd: Re: Creating new database]
  • From: Skylar Saveland
• DB terminating
  • From: Scott Felt
• Re: Can anyone help setting up pgbouncer?
  • From: Nick
• Re: pg_standby instructions
  • From: Joshua D. Drake
• pg_standby instructions
  • From: akp geek
• Re: Can anyone help setting up pgbouncer?
  • From: Richard Huxton
• Re: DB terminating
  • From: Scott Felt
• Re: Creating new database - SOLVED
  • From: John R Pierce
• Re: DB terminating
  • From: Tom Lane
• Re: passing parameters to multiple statements
  • From: Daniel Verite
• Re: DB terminating [on Windows]
  • From: Richard Broersma
• DB terminating
  • From: Scott Felt
• Re: Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard?
  • From: doug livesey
• Re: passing parameters to multiple statements
  • From: Pavel Stehule
• Re: Creating new database - SOLVED
  • From: Malcolm Warren
• Re: Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard?
  • From: doug livesey
• Re: Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard?
  • From: doug livesey
• Re: Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard?
  • From: Peter Hunsberger
• Re: passing parameters to multiple statements
  • From: Konstantin Izmailov
• Totally fresh uninstall/reinstall of Postgres on MacBook Pro running Snow Leopard?
  • From: doug livesey
• Re: Out of sync Primary Key Index
  • From: Bill Moran
• Re: Out of sync Primary Key Index
  • From: Adrian Klaver
• Out of sync Primary Key Index
  • From: Dave Coventry
• Re: Creating new database
  • From: Joao Ferreira gmail
• Re: Creating new database
  • From: Scott Marlowe
• [Fwd: Re: Creating new database]
  • From: Malcolm Warren
• Re: Creating new database
  • From: Joao Ferreira gmail
• Re: passing parameters to multiple statements
  • From: Thomas Kellerer
• Re: column does not exist error
  • From: Scott Marlowe
• advocating pgsql was:passing parameters to multiple statements
  • From: Ivan Sergio Borgonovo
• Re: column does not exist error
  • From: Thomas Markus
• Re: column does not exist error
  • From: Vidhya Bondre
• Re: Creating new database
  • From: Vidhya Bondre
• Re: passing parameters to multiple statements
  • From: Pavel Stehule
• Re: column does not exist error
  • From: Thomas Kellerer
• Re: column does not exist error
  • From: Naoko Reeves
• Re: column does not exist error
  • From: Raymond O'Donnell
• column does not exist error
  • From: Dave Coventry
• Re: Creating new database
  • From: Raymond O'Donnell
• Creating new database
  • From: Malcolm Warren
• Re: vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Thom Brown
• Re: passing parameters to multiple statements
  • From: Ivan Sergio Borgonovo
• vacuumdb: vacuuming of database "xy" failed: PANIC: corrupted item pointer: 19227
  • From: Tech 2010
• Re: passing parameters to multiple statements
  • From: Pavel Stehule
• Re: Data Directory size increasing abnormally
  • From: Joao Ferreira gmail
• Re: passing parameters to multiple statements
  • From: Ivan Sergio Borgonovo
• Re: Postgresql Database Lock Problem
  • From: shohorab hossain
• Re: Postgresql Database Lock Problem
  • From: shohorab hossain
• Re: Postgresql Database Lock Problem
  • From: shohorab hossain
• Re: cast record to array in plpgsql
  • From: Pavel Stehule
• Re: Where do you store key for encryption
  • From: David Wall
• Re: passing parameters to multiple statements
  • From: David Fetter
• Re: Where do you store key for encryption
  • From: Naoko Reeves
• Re: Where do you store key for encryption
  • From: Merlin Moncure
• Re: Error when creating table with boolean data type
  • From: Tom Lane
• Where do you store key for encryption
  • From: Naoko Reeves
• Re: Data Directory size increasing abnormally
  • From: Reid Thompson
• Re: Data Directory size increasing abnormally
  • From: Scott Marlowe
• Re: Data Directory size increasing abnormally
  • From: John R Pierce
• Re: Postgres Clustering Options
  • From: David Kerr
• Data Directory size increasing abnormally
  • From: utsav
• Re: Can anyone help setting up pgbouncer?
  • From: Nick
• cast record to array in plpgsql
  • From: Kurt
• Re: Experience with many schemas vs many databases
  • From: Loyal
• Re: Can anyone help setting up pgbouncer?
  • From: Nick
• Re: Error when creating table with boolean data type
  • From: APseudoUtopia
• Re: Error when creating table with boolean data type
  • From: William Carithers
• Error when creating table with boolean data type
  • From: William Carithers
• Re: does encrypt function support higher than basic ascii?
  • From: Naoko Reeves
• Re: does encrypt function support higher than basic ascii?
  • From: Richard Huxton
• Re: does encrypt function support higher than basic ascii?
  • From: Naoko Reeves
• Re: Postgresql Database Lock Problem
  • From: Scott Marlowe
• Re: Corrupt indices on already-dropped table (could not open relation with OID ...)
  • From: Craig de Stigter
• Re: does encrypt function support higher than basic ascii?
  • From: Naoko Reeves
• Re: does encrypt function support higher than basic ascii?
  • From: Richard Huxton
• Re: build array of composites in SPI
  • From: Merlin Moncure
• Re: Postgresql Database Lock Problem
  • From: Tom Lane
• does encrypt function support higher than basic ascii?
  • From: Naoko Reeves
• Re: [ADMIN] Postgresql Database Lock Problem
  • From: Plugge, Joe R.
• Postgresql Database Lock Problem
  • From: shohorab hossain
• Re: build array of composites in SPI
  • From: Tom Lane
• Re: build array of composites in SPI
  • From: Merlin Moncure
• Re: plperl: spi_query_prepared/spi_fetchrow versus spi_exec_prepared: memory?
  • From: Alexey Klyukin
• Re: build array of composites in SPI
  • From: Tom Lane
• build array of composites in SPI
  • From: Merlin Moncure
• impersonating a user/ownership problems
  • From: Ivan Sergio Borgonovo
• Re: passing parameters to multiple statements
  • From: Konstantin Izmailov
• Re: WAL file question
  • From: Geoffrey
• Re: WAL file question
  • From: Tom Lane
• Re: postgresql-8.4.1 compile error (with Sun Studio 11)
  • From: Tom Lane
• WAL file question
  • From: Geoffrey
• Re: calling a function over several rows
  • From: Merlin Moncure
• Re: Can anyone help setting up pgbouncer?
  • From: Richard Huxton
• Re: test data
  • From: Thomas Kellerer
• test data
  • From: Willy-Bas Loos
• postgresql-8.4.1 compile error (with Sun Studio 11)
  • From: Maciej (Matchek) Blizinski
• Re: Can anyone help setting up pgbouncer?
  • From: Rikard Bosnjakovic
• Re: Can anyone help setting up pgbouncer?
  • From: Nick
• Re: calling a function over several rows
  • From: Adam Rich
• plperl: spi_query_prepared/spi_fetchrow versus spi_exec_prepared: memory?
  • From: Nathan Jahnke
• Re: calling a function over several rows
  • From: Pavel Stehule
• Re: calling a function over several rows
  • From: Merlin Moncure
• calling a function over several rows
  • From: Adam Rich
• Re: specifying a password on the cmd line for db connect
  • From: Ashesh Vashi
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: Raymond C. Rodgers
• Re: Corrupt indices on already-dropped table (could not open relation with OID ...)
  • From: Tom Lane
• Corrupt indices on already-dropped table (could not open relation with OID ...)
  • From: Craig de Stigter
• Re: "money" binary representation
  • From: Andrew Chernow
• Re: "money" binary representation
  • From: Merlin Moncure
• Re: specifying a password on the cmd line for db connect
  • From: Raymond O'Donnell
• Re: specifying a password on the cmd line for db connect
  • From: Raymond O'Donnell
• Re: specifying a password on the cmd line for db connect
  • From: Greg Smith
• specifying a password on the cmd line for db connect
  • From: Gauthier, Dave
• Re: Update on Insert
  • From: Dann Corbit
• Re: Full Text Search 101?
  • From: Jonathan
• Update on Insert
  • From: Sebastian Feher
• Re: passing parameters to multiple statements
  • From: manitou-sig
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: John DeSoi
• Re: createdb errors and more
  • From: Scott Marlowe
• Re: createdb errors and more
  • From: Reno Bladergroen
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: Tom Lane
• Re: [HACKERS] Update on Insert
  • From: Thom Brown
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: John R Pierce
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: Raymond Rodgers
• Re: Need full search text on a shared hosting web site using 8.1.x
  • From: Tom Lane
• Re: createdb errors and more
  • From: Tom Lane
• Need full search text on a shared hosting web site using 8.1.x
  • From: Raymond Rodgers
• Re: What is the correct way to extract values from an int8 array in SPI?
  • From: Boszormenyi Zoltan
• Re: createdb errors and more
  • From: Joshua D. Drake
• Re: createdb errors and more
  • From: Rikard Bosnjakovic
• Re: Postgres issues "Not enough storage is available to complete this operation" exception
  • From: Bill Moran
• createdb errors and more
  • From: Reno Bladergroen
• Re: Postgres issues "Not enough storage is available to complete this operation" exception
  • From: Thom Brown
• Postgres issues "Not enough storage is available to complete this operation" exception
  • From: Maria Cianci
• Re: What is the correct way to extract values from an int8 array in SPI?
  • From: Alvaro Herrera
• Re: Experience with many schemas vs many databases
  • From: Peter Hunsberger
• Re: Comparing bit in an integer field
  • From: Amitabh Kant
• Re: safelly erasing dirs/files
  • From: Scott Marlowe
• Re: What is the correct way to extract values from an int8 array in SPI?
  • From: Tom Lane
• Re: Comparing bit in an integer field
  • From: Thom Brown
• Re: Comparing bit in an integer field
  • From: A. Kretschmer
• Re: Comparing bit in an integer field
  • From: Thom Brown
• Comparing bit in an integer field
  • From: Amitabh Kant
• Re: Customize the install directory of the postgres DB
  • From: Eric Comeau
• Re: [pgeu-general] pgday.eu
  • From: Thom Brown
• Re: [pgeu-general] pgday.eu
  • From: Dave Page
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Zdenek Kotala
• Re: [pgeu-general] pgday.eu
  • From: Thom Brown
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Zdenek Kotala
• Re: Experience with many schemas vs many databases
  • From: undisclosed user
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Loyal
• Re: Config help
  • From: Lew
• Re: Experience with many schemas vs many databases
  • From: Loyal
• Re: safelly erasing dirs/files
  • From: Jasen Betts
• Re: dumping parts of a database
  • From: A. Kretschmer
• Re: re-using RETURNING
  • From: Jasen Betts
• Re: Raise functionality
  • From: Jasen Betts
• Re: Backups
  • From: Jasen Betts
• Re: Absolute value of intervals
  • From: Jasen Betts
• dumping parts of a database
  • From: Malm Paul
• Re: passing parameters to multiple statements
  • From: Pavel Stehule
• What is the correct way to extract values from an int8 array in SPI?
  • From: Boszormenyi Zoltan
• Re: -c argument not recognized
  • From: Jasen Betts
• Re: "money" binary representation
  • From: Jasen Betts
• passing parameters to multiple statements
  • From: Konstantin Izmailov
• Re: "money" binary representation
  • From: Tom Lane
• Re: "money" binary representation
  • From: Konstantin Izmailov
• Re: "money" binary representation
  • From: John R Pierce
• "money" binary representation
  • From: Konstantin Izmailov
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Greg Smith
• Re: Triggering from a specific column update
  • From: Adrian Klaver
• When running pgsql2shp it truncates fields that are over 10 characters. How can I prevent this from occurring?
  • From: John Mitchell
• Re: Triggering from a specific column update
  • From: Tom Lane
• Re: Triggering from a specific column update
  • From: Bob Pawley
• Re: Triggering from a specific column update
  • From: Tom Lane
• Triggering from a specific column update
  • From: Bob Pawley
• Re: [pgeu-general] pgday.eu
  • From: Thom Brown
• Re: Config help
  • From: John R Pierce
• Re: Config help
  • From: BuyAndRead Test
• Re: Config help
  • From: Scott Marlowe
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Tom Lane
• Config help
  • From: BuyAndRead Test
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Simon Riggs
• Re: Experience with many schemas vs many databases
  • From: John R Pierce
• Re: Experience with many schemas vs many databases
  • From: undisclosed user
• Re: Voting: "pg_ctl init" versus "initdb"
  • From: Greg Smith
• Re: Experience with many schemas vs many databases
  • From: John R Pierce
• Re: Experience with many schemas vs many databases
  • From: Scott Marlowe
• Re: Experience with many schemas vs many databases
  • From: Merlin Moncure
• Re: Experience with many schemas vs many databases
  • From: Tom Lane
• Re: Fast Search on Encrypted Feild
  • From: Naoko Reeves
• Re: Fast Search on Encrypted Feild
  • From: Merlin Moncure
• Re: Experience with many schemas vs many databases
  • From: Johan Nel
• Re: Fast Search on Encrypted Feild
  • From: Alban Hertroys
• Re: Experience with many schemas vs many databases
  • From: Jorge Godoy
• Re: Experience with many schemas vs many databases
  • From: John R Pierce
• Experience with many schemas vs many databases
  • From: undisclosed user
• Re: re-using RETURNING
  • From: Andreas Kretschmer
• Re: safelly erasing dirs/files
  • From: John R Pierce
• Re: safelly erasing dirs/files
  • From: Greg Smith
• Re: all empty tables
  • From: Craig Ringer
• Re: safelly erasing dirs/files
  • From: Bill Todd
• Re: Fast Search on Encrypted Feild
  • From: Bill Moran
• Re: [pgeu-general] pgday.eu
  • From: Thom Brown
• Re: Upgrading databases
  • From: Greg Sabino Mullane
• Re: Fast Search on Encrypted Feild
  • From: John R Pierce
• Re: Fast Search on Encrypted Feild
  • From: Naoko Reeves
• Re: Fast Search on Encrypted Feild
  • From: Merlin Moncure
• Fast Search on Encrypted Feild
  • From: Naoko Reeves
• Re: all empty tables
  • From: Merlin Moncure
• Re: 8.5devel: alter constraint ?
  • From: Andreas Kretschmer
• Re: safelly erasing dirs/files
  • From: Greg Stark
• Re: 8.5devel: alter constraint ?
  • From: Jeff Davis
• Re: Remote Database Connection
  • From: John R Pierce
• Re: Remote Database Connection
  • From: Andreas Kretschmer
• Re: safelly erasing dirs/files
  • From: John R Pierce
• Re: safelly erasing dirs/files
  • From: Andreas Kretschmer
• Remote Database Connection
  • From: Nykolyn, Andy (AS)
• Re: safelly erasing dirs/files
  • From: John R Pierce
• Re: safelly erasing dirs/files
  • From: Joao Ferreira gmail
• Re: safelly erasing dirs/files
  • From: Greg Smith
• Re: safelly erasing dirs/files
  • From: Bill Moran
• Re: safelly erasing dirs/files
  • From: Tom Lane
• Re: safelly erasing dirs/files
  • From: A. Kretschmer
• Re: XLOG's implementation details
  • From: Erik Jones
• Re: safelly erasing dirs/files
  • From: Scott Mead
• safelly erasing dirs/files
  • From: Joao Ferreira gmail
• Re: XLOG's implementation details
  • From: Erik Jones
• If you wanna have some fun...
  • From: Chris Baechle
• Re: [pgeu-general] pgday.eu
  • From: Tim Landscheidt
• Re: [pgeu-general] pgday.eu
  • From: Thom Brown