On Saturday, March 29, 2014, Tom Lane wrote:
> Jeff Janes > writes:
> > But, it is hard to tell what the real solution is, because the doc
> doesn't
> > explain why it should refuse (and fail) to overwrite an existing file.
> The
> > only reason I can think of to make that recommendation is beca
Jeff Janes writes:
> But, it is hard to tell what the real solution is, because the doc doesn't
> explain why it should refuse (and fail) to overwrite an existing file. The
> only reason I can think of to make that recommendation is because it is
> easy to accidentally configure two clusters to a
On Fri, Mar 21, 2014 at 2:22 PM, MauMau wrote:
> From: "Jeff Janes"
>
> Do people really just copy the files from one directory of local storage
>> to
>> another directory of local storage? I don't see the point of that.
>>
>
> It makes sense to archive WAL to a directory of local storage for
On Sat, Mar 22, 2014 at 06:22:37AM +0900, MauMau wrote:
> From: "Jeff Janes"
> >Do people really just copy the files from one directory of local
> >storage to
> >another directory of local storage? I don't see the point of that.
>
> It makes sense to archive WAL to a directory of local storage f
On Fri, Mar 21, 2014 at 01:16:08PM -0700, Jeff Janes wrote:
> On Sun, Mar 16, 2014 at 3:23 AM, MauMau wrote:
>
> Hello,
>
> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> Windows) as an example for archive_command. However, cp/copy does not
> sync
> the
From: "Jeff Janes"
Do people really just copy the files from one directory of local storage
to
another directory of local storage? I don't see the point of that.
It makes sense to archive WAL to a directory of local storage for media
recovery. Here, the local storage is a different disk dr
On Sun, Mar 16, 2014 at 3:23 AM, MauMau wrote:
> Hello,
>
> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> Windows) as an example for archive_command. However, cp/copy does not sync
> the copied data to disk. As a result, the completed WAL segments would be
> lost in th
From: "Michael Paquier"
On Fri, Mar 21, 2014 at 8:54 PM, MauMau wrote:
* Create pg_copy in C so that it can be used on Windows as well as on
UNIX/Linux. It just copies one file. Its source code is located in
src/bin/pg_copy/. Please recommend a better name if you have one in
mind.
I'd rat
From: "Michael Paquier"
On Fri, Mar 21, 2014 at 8:54 PM, MauMau wrote:
* Create pg_copy in C so that it can be used on Windows as well as on
UNIX/Linux. It just copies one file. Its source code is located in
src/bin/pg_copy/. Please recommend a better name if you have one in
mind.
I'd rat
On Fri, Mar 21, 2014 at 8:54 PM, MauMau wrote:
> * Create pg_copy in C so that it can be used on Windows as well as on
> UNIX/Linux. It just copies one file. Its source code is located in
> src/bin/pg_copy/. Please recommend a better name if you have one in mind.
I'd rather see that as a part o
From: "Mitsumasa KONDO"
2014-03-17 21:12 GMT+09:00 Fujii Masao :
On Mon, Mar 17, 2014 at 10:20 AM, Robert Haas
wrote:
> On Sun, Mar 16, 2014 at 6:23 AM, MauMau wrote:
>> * Improve the example in the documentation.
>> But what command can we use to reliably sync just one file?
>>
>> * Provide
2014-03-17 21:12 GMT+09:00 Fujii Masao :
> On Mon, Mar 17, 2014 at 10:20 AM, Robert Haas
> wrote:
> > On Sun, Mar 16, 2014 at 6:23 AM, MauMau wrote:
> >> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> >> Windows) as an example for archive_command. However, cp/copy does
On Mon, Mar 17, 2014 at 10:20 AM, Robert Haas wrote:
> On Sun, Mar 16, 2014 at 6:23 AM, MauMau wrote:
>> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
>> Windows) as an example for archive_command. However, cp/copy does not sync
>> the copied data to disk. As a result, t
On Sun, Mar 16, 2014 at 7:53 PM, MauMau wrote:
> From: "Amit Kapila"
>
>> How about using pg_receivexlog for archiving purpose?
>
>
> pg_receivexlog is good in that it does fsync(). But it seems difficult to
> use correctly, and I'm not sure if I can catch all WAL segments without any
> loss. p
On Sun, Mar 16, 2014 at 6:23 AM, MauMau wrote:
> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> Windows) as an example for archive_command. However, cp/copy does not sync
> the copied data to disk. As a result, the completed WAL segments would be
> lost in the following
On 03/16/2014 03:23 PM, MauMau wrote:
From: "Amit Kapila"
How about using pg_receivexlog for archiving purpose?
pg_receivexlog is good in that it does fsync(). But it seems difficult
to use correctly, and I'm not sure if I can catch all WAL segments
without any loss. pg_receivexlog must be
On Sun, Mar 16, 2014 at 10:23 AM, MauMau wrote:
> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> Windows) as an example for archive_command. However, cp/copy does not sync
> the copied data to disk
I'm actually a lot less concerned about fsyncing the backup than I am
abo
From: "Amit Kapila"
How about using pg_receivexlog for archiving purpose?
pg_receivexlog is good in that it does fsync(). But it seems difficult to
use correctly, and I'm not sure if I can catch all WAL segments without any
loss. pg_receivexlog must be started with postmaster and monitored
On Sun, Mar 16, 2014 at 3:53 PM, MauMau wrote:
> Hello,
>
> The PostgreSQL documentation describes cp (on UNIX/Linux) or copy (on
> Windows) as an example for archive_command. However, cp/copy does not sync
> the copied data to disk. As a result, the completed WAL segments would be
> lost in the
19 matches
Mail list logo
