From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | postgres(dot)org(dot)nospam(at)mindcontrol(dot)org, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: Bug #789: Transaction Archival Logging -- Hot Backups |
Date: | 2002-09-29 05:19:28 |
Message-ID: | 200209290519.g8T5JS602576@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
I see in the pg_dump manual page:
pg_dump makes consistent backups even if the database is
being used concurrently. pg_dump does not block other
users accessing the database (readers or writers).
---------------------------------------------------------------------------
pgsql-bugs(at)postgresql(dot)org wrote:
> Jon Watte (postgres(dot)org(dot)nospam(at)mindcontrol(dot)org) 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 majordomo(at)postgresql(dot)org)
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
From | Date | Subject | |
---|---|---|---|
Next Message | pgsql-bugs | 2002-09-29 10:25:27 | Bug #790: Optimizer does not want to use an index for large table |
Previous Message | pgsql-bugs | 2002-09-29 04:37:25 | Bug #789: Transaction Archival Logging -- Hot Backups |