| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Joseph Shraibman'" <jks(at)selectacast(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Doug McNaught <doug(at)wireboard(dot)com>, pgsql-general(at)postgresql(dot)org |
| Subject: | RE: Re: Backups WAS: 2 gig file size limit |
| Date: | 2001-07-10 19:55:19 |
| Message-ID: | 3705826352029646A3E91C53F7189E320166BA@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> > pg_ctl stop
> > tar cfz - $PGDATA >someplace
> > pg_ctl start
> >
> But that would mean I would have to have all my programs
> detect that the database went down and make new connections.
You'd better to handle lost connections anyway.
> I would rather that postgres just lock all the files and
> do the tar.
Not suitable for online backup to bother with implementation.
We hope to have WAL-based backup and restore (BAR) in some
future.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Roderick A. Anderson | 2001-07-10 20:12:05 | Re: Performance tuning for linux, 1GB RAM, dual CPU? |
| Previous Message | ryan.a.roemmich | 2001-07-10 19:49:08 | RE: index skipped in favor of seq scan. |