| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
| Cc: | Alex Pilosov <alex(at)pilosoft(dot)com>, Mihai Gheorghiu <tanhq(at)bigplanet(dot)com>, pgsql-general(at)hub(dot)org |
| Subject: | Re: PostgreSQL capabilities |
| Date: | 2000-05-31 14:36:07 |
| Message-ID: | 200005311436.KAA02979@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> Alex Pilosov wrote:
> >
> > > http://networkdna.com/database/index.html mentions that PostgreSQL is
> > > capable of "Online backup". What does that exactly mean?
> >
> > It means Postgres can do a reliable backup (a consistent snapshot) of a
> > database without shutting down the database.
>
> Hmmm. My backup procedure, based on earlier discussions in this group,
> involves blocking all write-access during a pg_dump. That is effectively
> shutting down the database from my perspective. Is there a quicker way
> to take a consistent snapshot while still allowing writes?
With 6.5 and 7.0, pg_dump grabs a consistent snapshot of the database at
the time it starts, and dumps that. No reason to shut out users.
--
Bruce Momjian | http://www.op.net/~candle
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ed Loehr | 2000-05-31 15:16:37 | Trouble-free vacuum w/concurrent writes? (was "PostgreSQL capabilities") |
| Previous Message | Ed Loehr | 2000-05-31 14:26:51 | Re: PostgreSQL capabilities |