Re: Corner case in xlog stuff: what happens exactly at a
От | Simon Riggs |
---|---|
Тема | Re: Corner case in xlog stuff: what happens exactly at a |
Дата | |
Msg-id | 1154964971.2570.85.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Corner case in xlog stuff: what happens exactly at a seg boundary? (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Corner case in xlog stuff: what happens exactly at a seg boundary?
|
Список | pgsql-hackers |
On Sat, 2006-08-05 at 23:59 -0400, Tom Lane wrote: > 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. This is done right? Ping me back if there's anything more to add. -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
В списке pgsql-hackers по дате отправления: