pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
Determining current WAL
4+ messages / 3 participants
[nested] [flat]

* Determining current WAL
@ 2005-02-17 10:24  thomas.revell@powerconv.alstom.com
  0 siblings, 1 reply; 4+ messages in thread

From: thomas.revell@powerconv.alstom.com @ 2005-02-17 10:24 UTC (permalink / raw)
  To: pgsql-admin

Hi,

I'm currently looking at using WAL / PITR backups for a database, and I 
need to keep the backups as up to date as possible. As such, keeping a 
copy of the current WAL file, as suggested in the manual, would seem to be 
a very good idea. I'm slightly confused, though, about which file is the 
current. I had assumed that it would always be the highest numbered, but 
it seems that in some cases this is not always dated as the most recently 
modified (this seems to occur after taking a full backup during some of my 
test cases). My question, then is whether I was correct in my original 
assumption, or whether the current WAL is in fact the most recently 
modified.

Apologies if I'm missing something really obvious, but I've searched the 
mail archives and the web and haven't been able to find anything relevant.

Regards

Thomas Revell


:.________________
CONFIDENTIALITY : This  e-mail  and  any attachments are confidential and 
may be privileged. If  you are not a named recipient, please notify the 
sender immediately and do not disclose the contents to another person, use 
it for any purpose or store or copy the information in any medium.



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Determining current WAL
@ 2005-02-17 15:33  Tom Lane <tgl@sss.pgh.pa.us>
  parent: thomas.revell@powerconv.alstom.com
  0 siblings, 1 reply; 4+ messages in thread

From: Tom Lane @ 2005-02-17 15:33 UTC (permalink / raw)
  To: thomas.revell@powerconv.alstom.com; +Cc: pgsql-admin

thomas.revell@powerconv.alstom.com writes:
> I'm currently looking at using WAL / PITR backups for a database, and I 
> need to keep the backups as up to date as possible. As such, keeping a 
> copy of the current WAL file, as suggested in the manual, would seem to be 
> a very good idea. I'm slightly confused, though, about which file is the 
> current. I had assumed that it would always be the highest numbered,

No.  Go with the most-recently-modified.  Segment files are normally
created (or renamed into place) in advance of being needed.

There should probably be a cleaner/more reliable way of identifying
the active file ...

			regards, tom lane



^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Determining current WAL
@ 2005-02-17 15:36  thomas.revell@powerconv.alstom.com
  0 siblings, 0 replies; 4+ messages in thread

From: thomas.revell@powerconv.alstom.com @ 2005-02-17 15:36 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>; +Cc: pgsql-admin

OK, thanks.









thomas.revell@powerconv.alstom.com writes:
> I'm currently looking at using WAL / PITR backups for a database, and I 
> need to keep the backups as up to date as possible. As such, keeping a 
> copy of the current WAL file, as suggested in the manual, would seem to 
be 
> a very good idea. I'm slightly confused, though, about which file is the 

> current. I had assumed that it would always be the highest numbered,

No.  Go with the most-recently-modified.  Segment files are normally
created (or renamed into place) in advance of being needed.

There should probably be a cleaner/more reliable way of identifying
the active file ...

                                                 regards, tom lane




:._______________
CONFIDENTIALITY : This  e-mail  and  any attachments are confidential and 
may be privileged. If  you are not a named recipient, please notify the 
sender immediately and do not disclose the contents to another person, use 
it for any purpose or store or copy the information in any medium.




^ permalink  raw  reply  [nested|flat] 4+ messages in thread

* Re: Determining current WAL
@ 2005-02-23 01:25  Gaetano Mendola <mendola@bigfoot.com>
  parent: Tom Lane <tgl@sss.pgh.pa.us>
  0 siblings, 0 replies; 4+ messages in thread

From: Gaetano Mendola @ 2005-02-23 01:25 UTC (permalink / raw)
  To: Tom Lane <tgl@sss.pgh.pa.us>

Tom Lane wrote:
> thomas.revell@powerconv.alstom.com writes:
> 
>>I'm currently looking at using WAL / PITR backups for a database, and I 
>>need to keep the backups as up to date as possible. As such, keeping a 
>>copy of the current WAL file, as suggested in the manual, would seem to be 
>>a very good idea. I'm slightly confused, though, about which file is the 
>>current. I had assumed that it would always be the highest numbered,
> 
> 
> No.  Go with the most-recently-modified.  Segment files are normally
> created (or renamed into place) in advance of being needed.
> 
> There should probably be a cleaner/more reliable way of identifying
> the active file ...

Yes it was discussed during the attempt to create the log delivery to
another server in "replay" state, if the master was not responding then
it was usefull have a way to identify the active wal segment, at the time
I was identifing the current wall the last created one


Regards
Gaetano Mendola





^ permalink  raw  reply  [nested|flat] 4+ messages in thread


end of thread, other threads:[~2005-02-23 01:25 UTC | newest]

Thread overview: 4+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2005-02-17 10:24 Determining current WAL thomas.revell@powerconv.alstom.com
2005-02-17 15:33 ` Tom Lane <tgl@sss.pgh.pa.us>
2005-02-23 01:25   ` Gaetano Mendola <mendola@bigfoot.com>
2005-02-17 15:36 Re: Determining current WAL thomas.revell@powerconv.alstom.com

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox