Mailing lists [pgsql-hackers]

28 December 2012

• 00:28   Re: fix bgworkers in EXEC_BACKEND anarazel@anarazel.de
• 02:15   Re: Proposal: Store "timestamptz" of database creation on "pg_database" Stephen Frost
• 06:09   Re: fix bgworkers in EXEC_BACKEND Tom Lane
• 08:07   SPI API and exceptions Peter Eisentraut
• 08:08   Re: Performance Improvement by reducing WAL for Update Operation Kyotaro HORIGUCHI
• 08:15   Re: multiple CREATE FUNCTION AS items for PLs Peter Eisentraut
• 08:25   Re: multiple CREATE FUNCTION AS items for PLs Pavel Stehule
• 10:04   Re: Proposal: Store "timestamptz" of database creation on "pg_database" Dimitri Fontaine
• 10:21   Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs
• 11:27   Re: Performance Improvement by reducing WAL for Update Operation Amit Kapila
• 11:28   Re: Performance Improvement by reducing WAL for Update Operation Amit Kapila
• 11:43   pg_stat_statements: calls under-estimation propagation Daniel Farina
• 11:45   Re: enhanced error fields Pavel Stehule
• 11:55   Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs
• 12:03   Re: Performance Improvement by reducing WAL for Update Operation Simon Riggs
• 12:06   Re: Proposal: Store "timestamptz" of database creation on "pg_database" Fabrízio de Royes Mello
• 12:09   Re: multiple CREATE FUNCTION AS items for PLs Hannu Krosing
• 14:04   Re: enhanced error fields Stephen Frost
• 15:10   Re: enhanced error fields Pavel Stehule
• 15:23   Re: multiple CREATE FUNCTION AS items for PLs Andrew Dunstan
• 15:25   Re: SPI API and exceptions Tom Lane
• 15:32   Re: multiple CREATE FUNCTION AS items for PLs Tom Lane
• 15:53   Behaviour of bgworker with SIGHUP Guillaume Lelarge
• 15:57   Re: enhanced error fields Tom Lane
• 16:23   proposal: ANSI SQL 2011 syntax for named parameters Pavel Stehule
• 17:59   Re: pg_stat_statements: calls under-estimation propagation Peter Geoghegan
• 17:59   Re: XLByte* usage Alvaro Herrera
• 18:06   Whats the correct way to change trigdata->tg_relation Charles Gomes
• 18:09   Re: enhanced error fields Peter Geoghegan
• 18:22   Re: enhanced error fields Peter Geoghegan
• 18:25   Re: A stab at implementing better password hashing, with mixed results Alastair Turner
• 18:29   Re: multiple CREATE FUNCTION AS items for PLs Hannu Krosing
• 18:41   Re: enhanced error fields Pavel Stehule
• 18:45   Re: XLByte* usage Andres Freund
• 18:53   Re: Proposal: Store "timestamptz" of database creation on "pg_database" Josh Berkus
• 19:03   Re: enhanced error fields Peter Geoghegan
• 19:24   Re: enhanced error fields Pavel Stehule
• 19:33   Re: enhanced error fields Peter Geoghegan
• 19:56   Re: enhanced error fields Pavel Stehule
• 20:30   Re: enhanced error fields Peter Eisentraut
• 20:33   Re: Submission Review: User control over psql error stream Alastair Turner
• 20:34   Re: enhanced error fields Peter Eisentraut
• 20:35   Re: enhanced error fields Peter Geoghegan
• 20:40   Re: enhanced error fields Peter Eisentraut
• 20:40   Re: enhanced error fields Peter Geoghegan
• 20:41   Re: enhanced error fields Pavel Stehule
• 20:47   Re: enhanced error fields Peter Geoghegan
• 20:49   Re: foreign key locks Alvaro Herrera
• 20:55   Re: enhanced error fields Pavel Stehule
• 20:59   Re: enhanced error fields Peter Geoghegan
• 21:05   Re: multiple CREATE FUNCTION AS items for PLs Peter Eisentraut
• 21:19   Re: proposal: ANSI SQL 2011 syntax for named parameters Peter Eisentraut
• 21:41   Re: proposal: ANSI SQL 2011 syntax for named parameters Gavin Flower
• 21:53   Re: dynamic SQL - possible performance regression in 9.2 Peter Eisentraut
• 22:11   Re: dynamic SQL - possible performance regression in 9.2 Heikki Linnakangas
• 23:06   ILIKE vs indices James Cloos
• 23:35   Re: enhanced error fields Tom Lane
• 23:41   Re: ILIKE vs indices Tom Lane