From: | "Bender, Cheryl" <cbender(at)mriresearch(dot)org> |
---|---|
To: | "Christopher Browne" <cbbrowne(at)acm(dot)org>, <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Dumping partial database content |
Date: | 2004-07-02 21:03:23 |
Message-ID: | D5DB5D0D27171247AFEC9648EE98752F032125CB@KCEX2KV1.mri-kc.int |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
I see what you're saying. I thought it had worked, but when I looked at
the dump file there was no data. Thanks.
Cheryl Bender
-----Original Message-----
From: pgsql-admin-owner(at)postgresql(dot)org
[mailto:pgsql-admin-owner(at)postgresql(dot)org] On Behalf Of Christopher
Browne
Sent: Friday, July 02, 2004 2:15 PM
To: pgsql-admin(at)postgresql(dot)org
Subject: Re: [ADMIN] Dumping partial database content
Martha Stewart called it a Good Thing when cbender(at)mriresearch(dot)org
("Bender, Cheryl") wrote:
> Just wondering--is it possible to dump on a temporary table?
The temp table is only visible inside the context of the transaction
under which it was created.
A pg_dump session will create an independent transaction context, where
the table won't be visible, alas.
So you can't use pg_dump to dump the data out.
You may, however, use COPY to dump it out yourself.
select * into temp table foo from bar;
copy foo to '/tmp/foo_contents.txt';
--
If this was helpful, <http://svcs.affero.net/rm.php?r=cbbrowne> rate me
http://www.ntlug.org/~cbbrowne/postgresql.html
Rules of the Evil Overlord #50. "My main computers will have their own
special operating system that will be completely incompatible with
standard IBM and Macintosh powerbooks." <http://www.eviloverlord.com/>
---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?
From | Date | Subject | |
---|---|---|---|
Next Message | Michelle Konzack | 2004-07-02 21:22:20 | Re: 32mb scsi system |
Previous Message | Paul Gimpelj | 2004-07-02 21:00:09 | [admin] 32mb scsi system |