Re: Forcing current WAL file to be archived - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Forcing current WAL file to be archived
Date
Msg-id 200607251548.k6PFmFJ15899@momjian.us
Whole thread Raw
In response to Re: Forcing current WAL file to be archived  (Hannu Krosing <hannu@skype.net>)
Responses Re: Forcing current WAL file to be archived  (Hannu Krosing <hannu@skype.net>)
List pgsql-hackers
Hannu Krosing wrote:
> ?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.

Sorry, I was actually asking what use the offset would be to a user.

--  Bruce Momjian   bruce@momjian.us EnterpriseDB    http://www.enterprisedb.com
 + If your life is a hard drive, Christ can be your backup. +


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Forcing current WAL file to be archived
Next
From: Simon Riggs
Date:
Subject: Re: Forcing current WAL file to be archived