From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
---|---|
To: | Peter Geoghegan <pg(at)heroku(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: missing documentation for partial WAL files |
Date: | 2015-08-18 05:21:22 |
Message-ID: | CAB7nPqTWoOD9yqmcCPkfPr+ycN=5jtkWKwr25PZF3++CZW8Akw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, Aug 18, 2015 at 3:57 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
> On Mon, Aug 17, 2015 at 11:50 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>> The commit message for de76884 contains some important information about
>> the purpose and use of the new .partial WAL files. But I don't see
>> anything about this in the documentation or another user-visible place.
>> We should probably add something.
This makes sense, those files are exposed in the user's archives when
the end of a timeline is reached at promotion. I think that this
should be added in "Continuous archiving in standby" with a new
paragraph, as the first paragraph argues about archive_mode = 'always'
and the second about 'on'. What about the attached?
> Uh, some documentation around .ready files would be nice too.
Why? Users normally need to have no knowledge of that, those status
files are managed only by the backend.
--
Michael
Attachment | Content-Type | Size |
---|---|---|
20150818_doc_wal_partial.patch | text/x-diff | 1.1 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2015-08-18 05:32:42 | Re: jsonb array-style subscripting |
Previous Message | Jim Nasby | 2015-08-18 05:15:36 | Re: [PROPOSAL] VACUUM Progress Checker. |