Mailing lists [pgsql-hackers]

22 October 2009

• 01:50   Re: Prelim specs for parser hooks for plpgsql Itagaki Takahiro
• 02:06   Re: Controlling changes in plpgsql variable resolution Pavel Stehule
• 02:19   Re: Prelim specs for parser hooks for plpgsql Pavel Stehule
• 02:32   TRIGGER with WHEN clause Itagaki Takahiro
• 04:55   Re: Hot standby, prepared xacts, locks Heikki Linnakangas
• 06:04   Re: Hot standby, prepared xacts, locks Simon Riggs
• 06:42   Re: Hot standby, prepared xacts, locks Heikki Linnakangas
• 06:51   some possible parser cleaning: drop support column(table) syntax Pavel Stehule
• 07:22   Re: Hot standby, prepared xacts, locks Simon Riggs
• 10:03   Using views for row-level access control is leaky Heikki Linnakangas
• 10:05   Re: Controlling changes in plpgsql variable resolution Dimitri Fontaine
• 10:36   Re: Controlling changes in plpgsql variable resolution Pavel Stehule
• 10:51   Re: Using views for row-level access control is leaky Richard Huxton
• 11:01   Re: Using views for row-level access control is leaky Pavel Stehule
• 11:06   Re: Using views for row-level access control is leaky Heikki Linnakangas
• 11:13   Re: Using views for row-level access control is leaky Richard Huxton
• 11:15   Re: Using views for row-level access control is leaky Pavel Stehule
• 11:19   Re: Using views for row-level access control is leaky Richard Huxton
• 11:26   Re: Using views for row-level access control is leaky Pavel Stehule
• 11:26   Re: Using views for row-level access control is leaky Richard Huxton
• 11:30   Re: Using views for row-level access control is leaky Richard Huxton
• 12:05   Re: Using views for row-level access control is leaky Robert Haas
• 13:07   Application name patch - v3 Dave Page
• 13:07   Re: Using views for row-level access control is leaky Rod Taylor
• 13:32   B-tree leaf node structure edwardyf
• 14:00   client_lc_messages Alvaro Herrera
• 14:12   Re: some possible parser cleaning: drop support column(table) syntax Tom Lane
• 14:13   Re: Controlling changes in plpgsql variable resolution Andrew Dunstan
• 14:15   Re: Controlling changes in plpgsql variable resolution Robert Haas
• 14:22   Re: some possible parser cleaning: drop support column(table) syntax Pavel Stehule
• 14:58   Re: some possible parser cleaning: drop support column(table) syntax Tom Lane
• 15:01   Re: per table random-page-cost? Cédric Villemain
• 15:02   Re: some possible parser cleaning: drop support column(table) syntax Robert Haas
• 15:03   Re: per table random-page-cost? Cédric Villemain
• 15:14   Re: B-tree leaf node structure Tom Lane
• 15:16   Re: per table random-page-cost? Cédric Villemain
• 15:30   Re: some possible parser cleaning: drop support column(table) syntax Pavel Stehule
• 15:33   Re: per table random-page-cost? Robert Haas
• 15:37   Re: some possible parser cleaning: drop support column(table) syntax Tom Lane
• 15:47   Re: some possible parser cleaning: drop support column(table) syntax Pavel Stehule
• 16:35   table corrupted João Eugenio Marynowski
• 16:47   Re: Using views for row-level access control is leaky Marc Munro
• 18:22   Re: B-tree leaf node structure Jeff Davis
• 18:24   Re: per table random-page-cost? Greg Stark
• 18:27   Re: EvalPlanQual seems a tad broken Tom Lane
• 18:28   Re: Fwd: Reversing flow of WAL shipping Greg Stark
• 18:30   Re: per table random-page-cost? Josh Berkus
• 18:41   Re: per table random-page-cost? Kevin Grittner
• 18:49   Re: per table random-page-cost? Robert Haas
• 19:13   Re: Controlling changes in plpgsql variable resolution Dimitri Fontaine
• 20:25   Re: per table random-page-cost? Greg Stark
• 20:35   plpgsql EXECUTE will not set FOUND Dimitri Fontaine
• 22:08   Writeable CTEs, again Marko Tiikkaja
• 23:08   Re: per table random-page-cost? Joshua D. Drake
• 23:13   Re: plpgsql EXECUTE will not set FOUND Tom Lane
• 23:13   table corrupted João Eugenio Marynowski
• 23:16   Re: table corrupted Joshua D. Drake
• 23:59   Re: client_lc_messages Magnus Hagander