| From: | Dustin Sallings <dustin(at)spy(dot)net> |
|---|---|
| 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 17:35:29 |
| Message-ID: | Pine.SGI.3.95.1000531103456.19100A-100000@bleu.west.spy.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Wed, 31 May 2000, 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?
Use a filesystem that supports snapshotting.
--
SA, beyond.com My girlfriend asked me which one I like better.
pub 1024/3CAE01D5 1994/11/03 Dustin Sallings <dustin(at)spy(dot)net>
| Key fingerprint = 87 02 57 08 02 D0 DA D6 C8 0F 3E 65 51 98 D8 BE
L_______________________ I hope the answer won't upset her. ____________
| From | Date | Subject | |
|---|---|---|---|
| Next Message | mikeo | 2000-05-31 18:41:17 | TOP SESSIONS? |
| Previous Message | Ross Williamson | 2000-05-31 17:26:06 | psql error - pq_recvbuf: unexpected EOF on client connection |