From: Scott Marlowe <scott.marlowe@gmail.com>
To: Michael Monnerie <michael.monnerie@is.it-management.at>
Cc: pgsql-admin@postgresql.org
Subject: Re: 8.3.5 broken after power fail
Date: Sat, 21 Feb 2009 02:43:04 -0700
Message-ID: <dcc563d10902210143m5d05fa01ge4b3122693490269@mail.gmail.com> (raw)
In-Reply-To: <200902210923.37082@zmi.at>
References: <de3f3b06f55e4f88b0ced132435bcd96@webmail.zmi.at>
<0b99ef815980dac4a445e1eb1da0d130@webmail.zmi.at>
<dcc563d10902181354m5bfe6a14n1570c911ba26764f@mail.gmail.com>
<200902210923.37082@zmi.at>
On Sat, Feb 21, 2009 at 1:23 AM, Michael Monnerie
<michael.monnerie@is.it-management.at> wrote:
> Also a question: Because I must read all data, the psql client runs out
> of memory, trying to cache all the 10GB from that table. I circumvented
> this with selecting only parts of the table all the time. Is there a
> smart way to do such a select without caching the results in memory? Is
> that what temporary tables and "select into" are made for? I just want
> to know the recommended way for doing huge queries.
You can dump individual tables with pg_dump -t table1 -t table2. That
should work without running out of memory. And yeah, temp tables and
select into are a good way to get your data ready to be pg_dumped.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: scott.marlowe@gmail.com, michael.monnerie@is.it-management.at
Subject: Re: 8.3.5 broken after power fail
In-Reply-To: <dcc563d10902210143m5d05fa01ge4b3122693490269@mail.gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox