From: | Markus Bertheau <twanger(at)bluetwanger(dot)de> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | Theodore Petrosky <tedpet5(at)yahoo(dot)com>, Lucas Lain <lainl(at)aconectarse(dot)com>, pgsql-sql(at)postgresql(dot)org |
Subject: | Re: restoring database |
Date: | 2003-12-23 10:18:17 |
Message-ID: | 1072174696.4901.0.camel@yarrow.bertheau.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-sql |
В Пнд, 22.12.2003, в 18:53, scott.marlowe пишет:
> On Mon, 22 Dec 2003, Theodore Petrosky wrote:
>
> > As I am not someone with a lot of experience....
> > (depending on the size of the 'dumpall') I would
> > create a new database to suck up the 'all' then
> > pg_dump the table I really cared about.
> >
> > Obviously, if the dump_all is a terabyte database this
> > method is inconvenient.... (to say the least).
> >
> > However it will work.
>
> In the past I've used
>
> 'cat -n filename'|grep -4 database
>
> to find the starting points of individual databases etc... and then used
> split to break it into the exact right size pieces to do this.
That sounds like something pg_dump / pg_dumpall should be able to do
itself, don't you think?
--
Markus Bertheau <twanger(at)bluetwanger(dot)de>
From | Date | Subject | |
---|---|---|---|
Next Message | Chris Travers | 2003-12-23 13:13:04 | Re: INHERITS and Foreign keys |
Previous Message | Joop | 2003-12-23 09:25:42 | stored queries |