Timeline for PostgreSQL Write Ahead Logs Archive Mode
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 29, 2016 at 9:20 | vote | accept | John K. N. | ||
| Mar 29, 2016 at 7:01 | comment | added | John K. N. | Yes, I would prefer an answer for DBAs and I don't know why you come to think I'm a poltergeist. I phrased my question pretty adequate, explaining what I have and what I understand is happening. Thanks for your time. | |
| Mar 27, 2016 at 1:44 | comment | added | jjanes | PostgreSQL is not deleting your files. If you had left out the information about the thing which is deleting your files, it is baffling how you think that would have yielded better answers. The only possible answer is "The thing which is deleting your files is deleting your files the way it feels like, because that is the way it feels like doing it.". This is a forum for DBAs, not poltergeists. If you don't want an answer directed at DBAs, what exactly do you want? | |
| Mar 24, 2016 at 13:39 | comment | added | John K. N. | WALs are stored in the /pg_xlog/ directory. The backup (or replication, copy, archive) thereof are stored in the directory specified in the 'archive_command'. I am trying to figure out how it should work if I were to use a backup of the archived WAL files together with a copy of the dump created with pg_basebackup. I'm not running a cluster, just using the WAL portion to have PITR capabilities. I guess if I would have left Simpana portion out I would have gotten better answers, but it is part of the equation I'm trying to solve. | |
| Mar 24, 2016 at 9:21 | history | answered | jjanes | CC BY-SA 3.0 |