Mailing lists [pgsql-hackers]

28 December 2012

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