Re: Corner case in xlog stuff: what happens exactly at a seg boundary? - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Corner case in xlog stuff: what happens exactly at a seg boundary?
Date
Msg-id 18482.1154836780@sss.pgh.pa.us
Whole thread Raw
In response to Corner case in xlog stuff: what happens exactly at a seg boundary?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Corner case in xlog stuff: what happens exactly at a
Re: Corner case in xlog stuff: what happens exactly at a seg boundary?
List pgsql-hackers
I wrote:
> Rather than expecting user-level scripts to get this corner case
> right, I suggest that we ought to modify pg_stop_backup and friends
> so that what they return is the last used byte address of WAL, not
> the first unused byte address as now.  Then, blindly extracting
> the filename will give the right answer about which file to archive,
> even in the boundary case.

After further thought I desisted from that plan: changing the result
convention of existing functions like pg_stop_backup() will break any
existing archiving scripts that do get it right.  Instead, we can put
the boundary-case logic into the new functions that extract a filename
from the WAL location string that the action functions return.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: [PATCHES] Forcing current WAL file to be archived
Next
From: "Marc G. Fournier"
Date:
Subject: Re: 8.2 features status