Re: Forcing current WAL file to be archived
От | Hannu Krosing |
---|---|
Тема | Re: Forcing current WAL file to be archived |
Дата | |
Msg-id | 1153842113.2922.17.camel@localhost.localdomain обсуждение исходный текст |
Ответ на | Re: Forcing current WAL file to be archived (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: Forcing current WAL file to be archived
|
Список | pgsql-hackers |
Ühel kenal päeval, T, 2006-07-25 kell 11:27, kirjutas Bruce Momjian: > Hannu Krosing wrote: > > ?hel kenal p?eval, T, 2006-07-25 kell 10:51, kirjutas Bruce Momjian: > > > Where are we on these TODO items: > > > > > > > > o Add reporting of the current WAL file, perhaps as part of > > > partial log file archiving > > > > It would be nice to have a function that tells both filename and offset > > of current WAL file, so it would be possible to do live async streaming > > of up-to-subsecond changes without too much overhead. > > OK, "offset" added to TODO item. What would the offset give us? the offset returned by lseek() on the WAL file, that is the end of the part of the WAL file which has actually been written to. -- ---------------- Hannu Krosing Database Architect Skype Technologies OÜ Akadeemia tee 21 F, Tallinn, 12618, Estonia Skype me: callto:hkrosing Get Skype for free: http://www.skype.com
В списке pgsql-hackers по дате отправления: