| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joseph Shraibman <jks(at)selectacast(dot)net> |
| Cc: | Doug McNaught <doug(at)wireboard(dot)com>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Re: Backups WAS: 2 gig file size limit |
| Date: | 2001-07-10 02:07:41 |
| Message-ID: | 27750.994730861@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers pgsql-jdbc pgsql-patches |
Joseph Shraibman <jks(at)selectacast(dot)net> writes:
> Could a command be added that locks all the files, quickly tars them
> up, then releases the lock?
pg_ctl stop
tar cfz - $PGDATA >someplace
pg_ctl start
There is no possibility of anything less drastic, if you want to ensure
that the database files are consistent and not changing. Don't even
think about doing a partial dump of the $PGDATA tree, either. If you
don't have a pg_log that matches your data files, you've got nothing.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-07-10 02:27:06 | Re: Re: Backups WAS: 2 gig file size limit |
| Previous Message | Mike Castle | 2001-07-10 01:46:10 | Re: Re: Backups WAS: 2 gig file size limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2001-07-10 02:26:03 | Mozilla 1.0 release soon? |
| Previous Message | Mike Castle | 2001-07-10 01:46:10 | Re: Re: Backups WAS: 2 gig file size limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-07-10 02:27:06 | Re: Re: Backups WAS: 2 gig file size limit |
| Previous Message | Mike Castle | 2001-07-10 01:46:10 | Re: Re: Backups WAS: 2 gig file size limit |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Lockhart | 2001-07-10 02:27:06 | Re: Re: Backups WAS: 2 gig file size limit |
| Previous Message | Bruce Momjian | 2001-07-10 02:06:50 | Re: DROP CONSTRAINT (UNIQUE) preliminary support |