| From: | David Steele <david(at)pgmasters(dot)net> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Beena Emerson <memissemerson(at)gmail(dot)com>, tushar <tushar(dot)ahuja(at)enterprisedb(dot)com>, Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>, Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>, Jim Nasby <Jim(dot)Nasby(at)bluetreble(dot)com>, Kuntal Ghosh <kuntalghosh(dot)2007(at)gmail(dot)com>, Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: increasing the default WAL segment size |
| Date: | 2017-03-24 12:38:08 |
| Message-ID: | 72098036-dfcf-5b5d-7020-534ee50d2b1b@pgmasters.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 3/24/17 12:27 AM, Peter Eisentraut wrote:
> On 3/23/17 16:58, Stephen Frost wrote:
>> The backup tools need to also get the LSN from the pg_stop_backup and
>> verify that they have the WAL file associated with that LSN.
>
> There is a function for that.
>
>> They also
>> need to make sure that they have all of the WAL files between the
>> starting LSN and the ending LSN. Doing that requires understanding how
>> the files are named to make sure there aren't any missing.
>
> There is not a function for that, but there could be one.
A function would be nice, but tools often cannot depend on the database
being operational so it's still necessary to re-implement them. Having
a sane sequence in the WAL makes that easier.
--
-David
david(at)pgmasters(dot)net
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Aleksander Alekseev | 2017-03-24 12:47:09 | Re: WIP: Covering + unique indexes. |
| Previous Message | Stephen Frost | 2017-03-24 12:30:32 | Re: Monitoring roles patch |