Skip site navigation (1) Skip section navigation (2)

Re: postgresql.conf archive_command example

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Simon Riggs <simon(at)2ndquadrant(dot)com>
Cc: Robert Treat <rob(at)xzilla(dot)net>, Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov>, Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, Josh Berkus <josh(at)agliodbs(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: postgresql.conf archive_command example
Date: 2011-09-08 07:08:08
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Thu, Sep 8, 2011 at 3:26 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> On Thu, Sep 8, 2011 at 7:05 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>> That's an option. But I don't think that finding an existing file is so serious
>> problem.
> The recommendation should be that the archived files are never
> overwritten because that prevents a huge range of data loss bugs and
> kills them stone dead.

I'm OK with that default behavior of the executable. It's helpful if
the executable
supports overwrite-if-filesize-is-not-16MB option.


Fujii Masao
NTT Open Source Software Center

In response to

pgsql-hackers by date

Next:From: Fujii MasaoDate: 2011-09-08 08:36:38
Subject: pg_last_xact_insert_timestamp
Previous:From: davegDate: 2011-09-08 06:35:29
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group