Achilleas Mantzios <achill@xxxxxxxxxxxxxxxxxxxxx> writes: > 1) Do you find this behavior normal? It's normal operation. Once a WAL file is not needed anymore, it's typically renamed into place to be a future WAL file; that's cheaper than deleting the file and creating/filling a new one. So those ones that have older timestamps do not contain useful data right this instant, but they're ready to accept data once the write pointer advances to them. > 2) From now on, can we assume a monotonic relation between file names and creation times in order to base our maintenance scripts on this? I wouldn't. You risk deleting a file just as it starts to be used. You could possibly look into pg_control to see the current LSN and avoid touching any files >= that point, but of course this complicates the maintenance logic quite a bit. The larger issue here is that you're confusing the function of an archive area with that of the active WAL directory. The server will prune what is in the active WAL directory and does not want your help. In an archive directory, I'd expect the files to have monotonic timestamps corresponding to the times you copied them over to the archive, so you could rely on the timestamp sequence there. regards, tom lane -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
