| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Hannu Krosing <hannu(at)skype(dot)net> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgreSQL(dot)org>, Marko Kreen <markokr(at)gmail(dot)com> |
| Subject: | Re: Forcing current WAL file to be archived |
| Date: | 2006-07-25 15:27:55 |
| Message-ID: | 200607251527.k6PFRtS12172@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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?
--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2006-07-25 15:31:58 | Re: Forcing current WAL file to be archived |
| Previous Message | Tom Lane | 2006-07-25 15:26:21 | Re: Better name/syntax for "online" index creation |