Re: COPYable logs status

From: Martijn van Oosterhout <kleptog(at)svana(dot)org>
To: Andrew Dunstan <andrew(at)dunslane(dot)net>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: COPYable logs status
Date: 2007-06-08 13:35:12
Message-ID: 20070608133511.GA9818@svana.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, Jun 08, 2007 at 08:31:54AM -0400, Andrew Dunstan wrote:
> The situation with this patch is that I now have it in a state where I
> think it could be applied, but there is one blocker, namely that we do
> not have a way of preventing the interleaving of log messages from
> different backends, which leads to garbled logs. This is an existing
> issue about which we have had complaints, but it becomes critical for a
> facility the whole purpose of which is to provide logs in a format
> guaranteed to work with our COPY command.

The whole semantics of PIPEBUF should prevent garbling, as long as each
write is a complete set of lines and no more than PIPEBUF bytes long.
Have we determined the actual cause of the garbling?

Have a nice day,
--
Martijn van Oosterhout <kleptog(at)svana(dot)org> http://svana.org/kleptog/
> From each according to his ability. To each according to his ability to litigate.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alvaro Herrera 2007-06-08 13:43:55 Re: COPYable logs status
Previous Message Alvaro Herrera 2007-06-08 13:27:26 Re: Autovacuum launcher doesn't notice death of postmaster immediately

Browse pgsql-patches by date

  From Date Subject
Next Message Alvaro Herrera 2007-06-08 13:43:55 Re: COPYable logs status
Previous Message Alvaro Herrera 2007-06-08 13:27:26 Re: Autovacuum launcher doesn't notice death of postmaster immediately