Mailing lists [pgsql-hackers]

23 October 2009

• 01:26   Re: client_lc_messages Alvaro Herrera
• 01:38   Re: per table random-page-cost? Alvaro Herrera
• 02:34   Re: table corrupted João Eugenio Marynowski
• 02:53   Re: table corrupted Robert Haas
• 03:00   Re: table corrupted João Eugenio Marynowski
• 03:10   (WIP) VACUUM REWRITE - CLUSTER by ctid Itagaki Takahiro
• 04:10   Re: table corrupted Robert Haas
• 05:07   Re: client_lc_messages Peter Eisentraut
• 05:27   pre-proposal: type interfaces Jeff Davis
• 06:08   Re: per table random-page-cost? Joshua D. Drake
• 06:16   Re: table corrupted Joshua D. Drake
• 06:55   Re: (WIP) VACUUM REWRITE - CLUSTER by ctid Heikki Linnakangas
• 08:24   Re: plpgsql EXECUTE will not set FOUND Dimitri Fontaine
• 08:28   Re: table corrupted Dimitri Fontaine
• 08:28   Re: Controlling changes in plpgsql variable resolution Peter Eisentraut
• 08:30   Re: Using views for row-level access control is leaky Heikki Linnakangas
• 09:00   Re: Using views for row-level access control is leaky Simon Riggs
• 09:13   Re: Using views for row-level access control is leaky Pavel Stehule
• 09:23   Re: per table random-page-cost? Cédric Villemain
• 10:38   Re: Using views for row-level access control is leaky KaiGai Kohei
• 10:49   Re: Using views for row-level access control is leaky Simon Riggs
• 11:04   Re: Using views for row-level access control is leaky KaiGai Kohei
• 11:19   Re: SE-PgSQL developer documentation (Re: Reworks for Access Control facilities (r2363)) KaiGai Kohei
• 11:30   Re: Using views for row-level access control is leaky Heikki Linnakangas
• 11:40   Re: Using views for row-level access control is leaky Heikki Linnakangas
• 12:07   Re: Using views for row-level access control is leaky Richard Huxton
• 12:23   Re: per table random-page-cost? Robert Haas
• 13:23   Re: per table random-page-cost? Cédric Villemain
• 13:41   Re: EvalPlanQual seems a tad broken Tom Lane
• 13:52   Re: plpgsql EXECUTE will not set FOUND Tom Lane
• 14:04   Re: Using views for row-level access control is leaky Tom Lane
• 14:16   Re: plpgsql EXECUTE will not set FOUND Robert Haas
• 14:24   Re: Using views for row-level access control is leaky David Fetter
• 14:32   Re: plpgsql EXECUTE will not set FOUND Andrew Dunstan
• 14:34   Re: pre-proposal: type interfaces Tom Lane
• 14:42   Re: Using views for row-level access control is leaky Heikki Linnakangas
• 14:50   Re: plpgsql EXECUTE will not set FOUND Tom Lane
• 15:08   Re: plpgsql EXECUTE will not set FOUND Kevin Grittner
• 15:15   Re: Using views for row-level access control is leaky Kevin Grittner
• 15:28   Re: client_lc_messages Alvaro Herrera
• 15:46   Re: plpgsql EXECUTE will not set FOUND Merlin Moncure
• 15:50   Re: plpgsql EXECUTE will not set FOUND Robert Haas
• 16:02   Re: client_lc_messages Tom Lane
• 16:03   Re: Using views for row-level access control is leaky Simon Riggs
• 16:05   Re: plpgsql EXECUTE will not set FOUND Pavel Stehule
• 16:38   Re: plpgsql EXECUTE will not set FOUND Robert Haas
• 16:53   Re: client_lc_messages Magnus Hagander
• 17:17   Re: pre-proposal: type interfaces Greg Stark
• 19:16   Re: pre-proposal: type interfaces Tom Lane
• 19:27   Re: table corrupted João Eugenio Marynowski
• 20:25   Re: pre-proposal: type interfaces Tom Lane
• 20:40   Re: pre-proposal: type interfaces Jeff Davis
• 21:55   Re: pre-proposal: type interfaces Tom Lane
• 23:04   Re: per table random-page-cost? Josh Berkus
• 23:29   Statement Level Deferred Triggers Andres Freund