| From: | "Sandeep Chadha" <sandeep(at)newnetco(dot)com> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>, "pgsql-general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Hot Backup |
| Date: | 2002-10-07 17:21:06 |
| Message-ID: | 4AFE42D73ED1F345A576D3290FF8421C17674A@exchange.nnco.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
Hello to all the Doers of Postgres!!!
Last time I went through forums, people spoke highly about 7.3 and its capability to do hot backups. My problem is if the database goes down and I lose my main data store, then I will lose all transactions back to the time I did the pg_dump.
Other databases (i e Oracle) solves this by retaining their archive logs in some physically separate storage. So, when you lose your data, you can restore the data from back-up, and then apply your archive log, and avoid losing any committed transactions.
Postgresql has been lacking this all along. I've installed postgres 7.3b2 and still don't see any archive's flushed to any other place. Please let me know how is hot backup procedure implemented in current 7.3 beta(2) release.
Thanks.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jean-Luc Lachance | 2002-10-07 17:32:09 | Re: Efficient date range search? |
| Previous Message | Vincent Stoessel | 2002-10-07 17:14:31 | Postgresql's jdbc driver: 2.0 compliant? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jan Wieck | 2002-10-07 17:42:03 | Re: Parallel Executors [was RE: Threaded Sorting] |
| Previous Message | Alvaro Herrera | 2002-10-07 17:13:03 | BTree metapage lock and freelist structure |