From: | Ed Loehr <eloehr(at)austin(dot)rr(dot)com> |
---|---|
To: | Michael Meskes <meskes(at)postgresql(dot)org> |
Cc: | pgsql-general(at)hub(dot)org |
Subject: | Re: PostgreSQL capabilities |
Date: | 2000-06-01 13:49:28 |
Message-ID: | 393669E8.65E85607@austin.rr.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Michael Meskes wrote:
>
> On Wed, May 31, 2000 at 09:26:51AM -0500, Ed Loehr wrote:
> > 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?
>
> You mean write commands fail during backup? I never tried doing this but
> have some experience backing up a running Oracle system. Of course you
> cannot allow writes to the data files itself during backup, but they
> shouldn't fail IMO.
There was at least one pre-7.0, pre-24Dec1999 report that writes during
vacuum caused corruption (I couldn't find the post in deja the other
day). I have no idea if that is still true, nor have I tested it.
Regards,
Ed Loehr
From | Date | Subject | |
---|---|---|---|
Next Message | Ron Peterson | 2000-06-01 13:49:56 | Re: Re: Speed of locating tables |
Previous Message | The Hermit Hacker | 2000-06-01 12:58:35 | Re: [HACKERS] Oft Ask: How to contribute to PostgreSQL? |