Re: Forcing current WAL file to be archived
От | Simon Riggs |
---|---|
Тема | Re: Forcing current WAL file to be archived |
Дата | |
Msg-id | 1155124565.2368.95.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Forcing current WAL file to be archived (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Forcing current WAL file to be archived
Re: Forcing current WAL file to be archived |
Список | pgsql-patches |
On Sat, 2006-08-05 at 23:57 -0400, Tom Lane wrote: > I also made the new user-level functions a bit > more orthogonal, so that filenames could be extracted from the > existing functions like pg_stop_backup. Something Hannu wrote has just reminded me that pg_current_xlog_location() returns the current Insert pointer rather than the current Write pointer. That would not be useful for streaming xlog records would it? Methinks it should be the Write pointer all of the time, since I can't think of a valid reason for wanting to know where the Insert pointer is *before* we've written to the xlog file. Having it be the Insert pointer could lead to some errors. Any objections if I correct that? -- Simon Riggs EnterpriseDB http://www.enterprisedb.com
В списке pgsql-patches по дате отправления: