Mailing lists [pgsql-hackers]

7 November 2009

• 00:14   Re: Quoting oddities when defining operators in postgres 8.3 Tom Lane
• 00:18   Re: plperl and inline functions -- first draft Tom Lane
• 00:20   Re: plperl and inline functions -- first draft Andrew Dunstan
• 00:47   Re: operator exclusion constraints Jeff Davis
• 01:20   Re: operator exclusion constraints Tom Lane
• 01:23   Re: operator exclusion constraints Tom Lane
• 01:38   Re: plperl and inline functions -- first draft Joshua Tolley
• 01:44   Re: operator exclusion constraints Andrew Dunstan
• 01:45   Re: Specific names for plpgsql variable-resolution control options? David E. Wheeler
• 01:53   Re: plperl and inline functions -- first draft Andrew Dunstan
• 01:55   Re: operator exclusion constraints Tom Lane
• 01:57   Re: Specific names for plpgsql variable-resolution control options? Tom Lane
• 02:10   Re: Specific names for plpgsql variable-resolution control options? David E. Wheeler
• 06:11   Re: Why do OLD and NEW have special internal names? David Fetter
• 06:24   Re: Specific names for plpgsql variable-resolution control options? Pavel Stehule
• 09:37   Getting consistent snapshot in multiple backends, for parallel pg_dump Heikki Linnakangas
• 10:47   Re: Getting consistent snapshot in multiple backends, for parallel pg_dump Simon Riggs
• 11:33   Uninitialized Data in WAL records generated in heap_(insert|update|delete) Andres Freund
• 17:47   Re: operator exclusion constraints Jeff Davis
• 17:57   Re: operator exclusion constraints Jeff Davis
• 18:08   Re: operator exclusion constraints Tom Lane
• 18:14   Re: operator exclusion constraints Robert Haas
• 18:29   Re: operator exclusion constraints David E. Wheeler
• 18:44   Re: operator exclusion constraints Jeff Davis
• 21:02   Re: Specific names for plpgsql variable-resolution control options? Sergio A. Kessler