Re: Forcing current WAL file to be archived - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 10265.1153840964@sss.pgh.pa.us
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Forcing current WAL file to be archived  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> I assumed we would have a function like pg_finish_wal_segment(), and
> server stop and stop_backup would call it too,

That idea is *exactly* what I'm objecting to.

> the reason being, it
> would greatly simplify our documentation on how to use PITR if these
> were done automatically.

No it wouldn't, it'd just bloat the already excessive WAL volume.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: Forcing current WAL file to be archived
Next
From: Hannu Krosing
Date:
Subject: Re: Forcing current WAL file to be archived