vBulletin Search Engine Optimization
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi, Tom Lane <tgl@sss.pgh.pa.us> wrote: > "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> writes: > > The WAL files have names like this: > > 00000001000000010000003C > > > I am wonder what the meaning of the two 1 in the filename is? > > The first one (the first 8 hex digits actually) are the current > "timeline" number. The second one isn't very interesting, it's > an artifact of the way that WAL file locations are converted to > file names internally. thanks for this information. > > > Are the WAL > > file names counted up to FFFFFFFFFFFFFFFFFFFFFFFFF ? > > Then I'll run into problems anyways as these int number are too large to be > > handled by bash. > > You definitely should not expect to convert the names to integers. Then I do not understand why only the names of the first and the last WAL file are stored in the backup history file. I assumed that when I count from the first to the last I catch all WAL files needed for a complete backup. Then I have no idea how to figure out, which of the WAL files are needed for the backup job. Or do I have to handle this via the file modification timestamps? does anybody has a pointer to documentation where I can read up about how the names of the WAL files are created/used in postgres? thanks Sebastian ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |
| ||||
| "Sebastian Reitenbach" <sebastia@l00-bugdead-prods.de> writes: > Tom Lane <tgl@sss.pgh.pa.us> wrote: >> You definitely should not expect to convert the names to integers. > Then I do not understand why only the names of the first and the last WAL > file are stored in the backup history file. You can compare the filenames as strings (at least in C locale this works fine). regards, tom lane ---------------------------(end of broadcast)--------------------------- TIP 9: In versions below 8.0, the planner will ignore your desire to choose an index scan if your joining column's datatypes do not match |