Re: postgresql.conf archive_command example - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: postgresql.conf archive_command example
Date
Msg-id CAHGQGwG_KcHHRYpdtETOTz7Mti9SuGBWhGjgdc_4EnmTW9gDJg@mail.gmail.com
Whole thread Raw
In response to Re: postgresql.conf archive_command example  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
On Thu, Sep 8, 2011 at 3:26 PM, Simon Riggs <simon@2ndquadrant.com> wrote:
> On Thu, Sep 8, 2011 at 7:05 AM, Fujii Masao <masao.fujii@gmail.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.

Regards,

-- 
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center


pgsql-hackers by date:

Previous
From: daveg
Date:
Subject: Re: FATAL: lock AccessShareLock on object 0/1260/0 is already held
Next
From: Fujii Masao
Date:
Subject: pg_last_xact_insert_timestamp