Re: [patch] pg_copy - a command for reliable WAL archiving - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [patch] pg_copy - a command for reliable WAL archiving
Date
Msg-id 9715.1408545400@sss.pgh.pa.us
Whole thread Raw
In response to Re: [patch] pg_copy - a command for reliable WAL archiving  (Andres Freund <andres@2ndquadrant.com>)
Responses Re: [patch] pg_copy - a command for reliable WAL archiving
List pgsql-hackers
Andres Freund <andres@2ndquadrant.com> writes:
> On 2014-08-20 10:19:33 -0400, Tom Lane wrote:
>> Alternatively, you could use the process PID as part of the temp file
>> name; which is probably a good idea anyway.

> I think that's actually worse, because nothing will clean up those
> unless you explicitly scan for all <whatever>.$pid files, and somehow
> kill them.

True.  As long as the copy command is prepared to get rid of a
pre-existing target file, using a fixed .tmp extension should be fine.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: [patch] pg_copy - a command for reliable WAL archiving
Next
From: Tom Lane
Date:
Subject: Re: jsonb format is pessimal for toast compression