Jon Watte ([EMAIL PROTECTED]) reports a bug with a severity of 2
The lower the number the more severe it is.
Short Description
Transaction Archival Logging -- Hot Backups
Long Description
I see no mention of transaction archival logging in the documentation.
This means that, even though you support correct transaction rollback semantics, to
back up the database in a consistent manner, I have to take it offline and backup all
the files.
Either I'm missing something (and I did a documentation, FAQ and Todo search) or it's
not currently possibly to actually put Postgres into a 24/7 production environment?
Sample Code
No file was uploaded with this report
---------------------------(end of broadcast)---------------------------
TIP 2: you can get off all lists at once with the unregister command
(send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
