From: | Frank Wittig <fw(at)weisshuhn(dot)de> |
---|---|
To: | Johannes Konert <jkonert(at)t3go(dot)de> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: pg_xlog - files are guaranteed to be sequentialy named? |
Date: | 2007-06-13 18:35:04 |
Message-ID: | 467038D8.7070504@weisshuhn.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Hello Johannes,
Johannes Konert schrieb:
> Thus the newest WAL xlog-file is on top and I can delete all not needed
> files at the bottom of the list.
You're using pg_controldata to figure out which file's serial is older
than the latest redo checkpoint.
In case of restart of the slave server PgSQL needs all files that were
archived beginning with the one right after the latest redo checkpoint
or it will fail to sync to its master.
> What happens if the 24hexdigits reach upper bound?
Did you calculate you question? I assume no.
24 Hex digits means 24^16 unique file names. Assuming your server saves
a WAL file each second (you should review your config it it does) it
takes (24^16)/(60*60*24*365)=3.84214066×10^14 years to reach the upper
bound. (Plase forgive me ignoring leap years ;))
I assume that there will be a system change before that date so counting
will start over again. ;)
Greetings,
Frank Wittig
From | Date | Subject | |
---|---|---|---|
Next Message | Ben | 2007-06-13 18:36:36 | Re: changing the /tmp/ lock file? |
Previous Message | Oisin Glynn | 2007-06-13 18:33:22 | Re: PostGreSQL for a small Desktop Application |