Re: COPYable logs status

From: Andrew Sullivan <ajs(at)crankycanuck(dot)ca>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Re: COPYable logs status
Date: 2007-06-08 15:04:26
Message-ID: 20070608150426.GE17144@phlogiston.dyndns.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Fri, Jun 08, 2007 at 10:29:03AM -0400, Tom Lane wrote:
>
> The only solution that I can see is to invent some sort of simple
> protocol for the syslogger pipe.

Perhaps having a look at the current IETF syslog discussion will be
helpful in that case? (I know it's not directly relevant, but maybe
others have thought about some of these things. I haven't read the
draft, note.)

http://tools.ietf.org/html/draft-ietf-syslog-protocol-20

There's also the discussion of reliability in RFC 3195:

ftp://ftp.rfc-editor.org/in-notes/rfc3195.txt

A

--
Andrew Sullivan | ajs(at)crankycanuck(dot)ca
The whole tendency of modern prose is away from concreteness.
--George Orwell

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Sullivan 2007-06-08 15:06:09 Re: Controlling Load Distributed Checkpoints
Previous Message Alvaro Herrera 2007-06-08 15:00:50 Re: BUG #3326: Invalid lower bound of autovacuum_cost_limit

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Sullivan 2007-06-08 15:06:09 Re: Controlling Load Distributed Checkpoints
Previous Message Alvaro Herrera 2007-06-08 15:00:50 Re: BUG #3326: Invalid lower bound of autovacuum_cost_limit