Re: Forcing current WAL file to be archived
От | Tom Lane |
---|---|
Тема | Re: Forcing current WAL file to be archived |
Дата | |
Msg-id | 27727.1155394753@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: Forcing current WAL file to be archived (Hannu Krosing <hannu@skype.net>) |
Ответы |
Re: Forcing current WAL file to be archived
|
Список | pgsql-patches |
Hannu Krosing <hannu@skype.net> writes: > Ühel kenal päeval, K, 2006-08-09 kell 10:57, kirjutas Tom Lane: >> Insert points to the next byte to be written within the internal WAL >> buffers. The byte(s) preceding it haven't necessarily gotten out of >> those buffers yet. Write points to the end of what we've actually >> written to the kernel, > I assume that it also points to the byte after what is written to > kernel, or is it tha last byte written ? Right, it's really first-unwritten-byte for all three pointers. The two newly added functions to convert WAL locations to filenames use XLByteToPrevSeg(), so they should do the right thing here (see comments in src/include/access/xlog_internal.h). regards, tom lane
В списке pgsql-patches по дате отправления: