Re: Re: Backups WAS: 2 gig file size limit

From: Joseph Shraibman <jks(at)selectacast(dot)net>
To: 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" <pgsql-general(at)postgresql(dot)org>
Subject: Re: Re: Backups WAS: 2 gig file size limit
Date: 2001-07-10 19:33:29
Message-ID: 3B4B5889.52D4220B@selectacast.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers pgsql-jdbc pgsql-patches

Tom Lane wrote:
>
> 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
>
But that would mean I would have to have all my programs detect that the
database went down and make new connections. I would rather that
postgres just lock all the files and do the tar.

--
Joseph Shraibman
jks(at)selectacast(dot)net
Increase signal to noise ratio. http://www.targabot.com

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Joseph Shraibman 2001-07-10 19:40:12 Re: Re: Backups WAS: 2 gig file size limit
Previous Message Allan Engelhardt 2001-07-10 19:09:40 Re: Encrypting database?

Browse pgsql-hackers by date

  From Date Subject
Next Message Joseph Shraibman 2001-07-10 19:40:12 Re: Re: Backups WAS: 2 gig file size limit
Previous Message Nathan Myers 2001-07-10 19:26:22 Re: AW: pg_index.indislossy

Browse pgsql-jdbc by date

  From Date Subject
Next Message Joseph Shraibman 2001-07-10 19:40:12 Re: Re: Backups WAS: 2 gig file size limit
Previous Message Steve Wampler 2001-07-10 18:07:53 Re: Too much data received?

Browse pgsql-patches by date

  From Date Subject
Next Message Joseph Shraibman 2001-07-10 19:40:12 Re: Re: Backups WAS: 2 gig file size limit
Previous Message Barry Lind 2001-07-10 18:07:46 Re: Shutdown hook imp