Mailing lists [pgsql-general]

5 February 2005

• 00:00   Re: Safely Killing Backends (Was: Applications that leak connections) Jim Wilson
• 00:35   Re: Safely Killing Backends (Was: Applications that leak connections) Tom Lane
• 00:49   Re: plpgsql function errors Martijn van Oosterhout
• 01:04   Re: Safely Killing Backends (Was: Applications that leak connections) Jim Wilson
• 01:25   Re: Safely Killing Backends (Was: Applications that leak connections) Alvaro Herrera
• 01:44   Re: Safely Killing Backends (Was: Applications that leak connections) Tom Lane
• 02:04   Re: error-tolerant COPY FROM Christopher Browne
• 02:55   Re: Duration between two timestamps phil campaigne
• 03:20   Re: Applications that leak connections Paul Tillotson
• 04:37   Re: Safely Killing Backends (Was: Applications that leak connections) Jim Wilson
• 04:44   Re: Safely Killing Backends (Was: Applications that leak connections) Jim Wilson
• 06:09   Re: plpgsql function errors Juan Casero (FL FLC)
• 06:19   Re: Is there a peer-to-peer server solution with PG? Tzahi Fadida
• 07:00   Can pg_restore also disable table CHECK contraint? CN
• 13:51   Re: Update command too slow Venkatesh Babu
• 14:15   Re: Update command too slow Venkatesh Babu
• 14:21   How many connections now ? NTPT
• 14:25   Re: How many connections now ? Devrim GUNDUZ
• 17:59   Re: Update command too slow Greg Stark
• 18:52   Re: is this index bloat? Christopher Browne
• 18:52   Re: pgpool 2.5b2 released Christopher Browne
• 18:52   Re: how to release a transaction lock on a table? Christopher Browne
• 19:08   pgpool simple feature request Joshua D. Drake
• 19:57   Re: Update command too slow Tom Lane
• 23:04   Re: Is there a peer-to-peer server solution with PG? Jan Wieck