Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support - Mailing list pgsql-bugs

From Euler Taveira
Subject Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support
Date
Msg-id 5103D7B4.4090800@timbira.com
Whole thread Raw
In response to Re: BUG #6528: pglesslog still referenced in docs, but no 9.1 support  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-bugs
On 25-01-2013 20:23, Jeff Janes wrote:
> I've been thinking about that.  Should pg_clearxlogtail for 9.3 only
> work for logs from 9.3, or should it be arranged to work on logs from
> older versions as well (which probably means parts of the 9.2 headers
> would need to be copied into the body of pg_clearxlogtail)?
>
As it is a new tool for contrib, I don't see the obligation to maintain
compatibility with prior versions unless someone want to do that legwork. If
the compatibility won't be included, the docs could point out the source for
prior versions.

> This is what I use:
>
> archive_command = 'set -C -o pipefail;
> (/usr/local/pgsql9_2/bin/pg_clearxlogtail < %p || cat %p)  | gzip >
> /mnt/foo/archivelog9_2/%f.gz'
>
> The "|| cat %p" business is because pg_clearxlogtail will fail on
> .history files and so needs an alternative path.
>
That's something that should be addressed, no?

> I think it would be better to have pg_clearxlogtail instead just
> silently pass any unrecognized files through without manipulation,
> rather than erroring out.
>
... or let people choose one or another.


--
   Euler Taveira de Oliveira - Timbira       http://www.timbira.com.br/
   PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento

pgsql-bugs by date:

Previous
From: electricboy98@yahoo.com
Date:
Subject: BUG #7827: Postgresql Porblem
Next
From: Jan Urbański
Date:
Subject: Re: cache lookup failed from empty plpythonu function