Mailing lists [pgsql-hackers]

6 October 2008

• 00:13   parallel pg_restore design issues Andrew Dunstan
• 01:50   Re: Add default_val to pg_settings Greg Smith
• 03:04   Re: parallel pg_restore design issues Philip Warner
• 06:59   Re: Subtransaction commits and Hot Standby Simon Riggs
• 07:02   Re: pgsql: Add relation fork support to pg_relation_size() function. Heikki Linnakangas
• 08:02   Re: pgsql: Add relation fork support to pg_relation_size() function. Magnus Hagander
• 08:25   Updates of SE-PostgreSQL 8.4devel patches (r1081) KaiGai Kohei
• 08:27   About postgresql8.3.3 build in MS VS2005 iihero
• 08:32   Re: pgsql: Add relation fork support to pg_relation_size() function. Gregory Stark
• 08:42   Re: About postgresql8.3.3 build in MS VS2005 Magnus Hagander
• 09:33   Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Guillaume Lelarge
• 10:33   Re: pgsql: Add relation fork support to pg_relation_size() function. Heikki Linnakangas
• 10:46   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Heikki Linnakangas
• 10:48   Re: pgsql: Add relation fork support to pg_relation_size() function. Greg Stark
• 11:43   Re: About postgresql8.3.3 build in MS VS2005 iihero
• 11:46   Re: About postgresql8.3.3 build in MS VS2005 Magnus Hagander
• 12:03   Re: pgsql: Add relation fork support to pg_relation_size() function. Tom Lane
• 12:23   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Tom Lane
• 12:28   Re: About postgresql8.3.3 build in MS VS2005 Tom Lane
• 12:29   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Guillaume Lelarge
• 12:38   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Heikki Linnakangas
• 12:49   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Tom Lane
• 13:07   Re: Add default_val to pg_settings Magnus Hagander
• 13:36   ctelevelsup is kind of a pain in the neck Tom Lane
• 13:54   Monitoring postgres Kellyton Campos Feitosa - GYN
• 14:01   Shouldn't pg_settings.enumvals be array of text? Tom Lane
• 14:08   Re: Shouldn't pg_settings.enumvals be array of text? Magnus Hagander
• 14:16   Re: Shouldn't pg_settings.enumvals be array of text? Tom Lane
• 14:24   Re: Shouldn't pg_settings.enumvals be array of text? Alvaro Herrera
• 14:48   Re: Shouldn't pg_settings.enumvals be array of text? Magnus Hagander
• 14:54   Re: Shouldn't pg_settings.enumvals be array of text? Alvaro Herrera
• 15:47   Re: Monitoring postgres Steve Crawford
• 16:00   Displaying references to fields of record variables Tom Lane
• 16:01   subcribe bull@pubbs.net
• 17:02   Re: Shouldn't pg_settings.enumvals be array of text? Greg Smith
• 18:42   Re: Add default_val to pg_settings Decibel!
• 18:51   Re: Common Table Expressions applied; some issues remain Decibel!
• 18:51   Re: FSM rewrite committed, loose ends Decibel!
• 18:51   Re: Bad error message Decibel!
• 18:51   Re: Ad-hoc table type? Decibel!
• 18:51   Re: Foreign key constraint for array-field? Decibel!
• 19:24   Re: Weird behaviour with ALTER TABLE ... SET TABLESPACE ... statement Heikki Linnakangas
• 20:04   Re: Common Table Expressions applied; some issues remain Robert Haas
• 20:39   query path, and rules Grzegorz Jaskiewicz
• 21:01   Transactions and temp tables Emmanuel Cecchet
• 21:05   Reducing some DDL Locks to ShareLock Simon Riggs
• 21:47   problems with initdb after last cvs up Grzegorz Jaskiewicz
• 22:57   Re: Reducing some DDL Locks to ShareLock Tom Lane
• 23:02   Re: Shouldn't pg_settings.enumvals be array of text? Tom Lane