Mailing lists [pgsql-hackers]

22 March 2005

• 00:27   Re: Proposal: OUT parameters for plpgsql Greg Stark
• 00:30   Re: Proposal: OUT parameters for plpgsql Jim C. Nasby
• 00:32   Re: Avoiding unnecessary writes during relation drop and Simon Riggs
• 02:44   Re: Proposal: OUT parameters for plpgsql Tom Lane
• 03:40   Re: Proposal: OUT parameters for plpgsql Gavin Sherry
• 04:30   Re: Proposal: OUT parameters for plpgsql Tom Lane
• 04:36   Re: Proposal: OUT parameters for plpgsql Christopher Kings-Lynne
• 04:54   Re: Proposal: OUT parameters for plpgsql Tom Lane
• 04:58   Re: Proposal: OUT parameters for plpgsql Gavin Sherry
• 05:03   Re: Proposal: OUT parameters for plpgsql Tom Lane
• 06:13   psql and pg_dump using obselete copy commands Christopher Kings-Lynne
• 06:16   Re: Prevent conflicting SET options from being set Qingqing Zhou
• 06:37   Using new copy libpq functions on a v2 protocol backend Christopher Kings-Lynne
• 07:20   Re: Proposal: OUT parameters for plpgsql Greg Stark
• 08:56   locks in CREATE TRIGGER, ADD FK Neil Conway
• 09:10   Re: locks in CREATE TRIGGER, ADD FK Neil Conway
• 09:32   Re: Proposal: OUT parameters for plpgsql Pavel Stehule
• 12:07   Re: caches lifetime with SQL vs PL/PGSQL procs strk@refractions.net
• 12:12   Re: what to do with backend flowchart Dave Page
• 14:33   Failed to re-find parent key Peter Eisentraut
• 17:55   Re: Failed to re-find parent key Tom Lane
• 17:57   Re: Failed to re-find parent key Alvaro Herrera
• 18:05   Re: Failed to re-find parent key Tom Lane
• 18:54   Re: Failed to re-find parent key Peter Eisentraut
• 23:09   Permissions on tables and views subhash@nmsu.edu