From: Tom Lane <tgl@sss.pgh.pa.us>
To: Chris Hoover <revoohc@sermonaudio.com>
Cc: PostgreSQL Admin <pgsql-admin@postgresql.org>
Subject: Re: Copying large tables with DBLink
Date: Thu, 24 Mar 2005 14:40:22 -0500
Message-ID: <5020.1111693222@sss.pgh.pa.us> (raw)
In-Reply-To: <42430E20.1010600@sermonaudio.com>
References: <42430E20.1010600@sermonaudio.com>
"Chris Hoover" <revoohc@sermonaudio.com> writes:
> Has anyone had problems with memory exhaustion and dblink? We were
> trying to use dblink to convert our databases to our new layout, and had
> our test server lock up several times when trying to copy a table that
> was significantly larger than our memory and swap.
You're not going to be able to do that with dblink, nor any other
set-returning function, because the current implementation of SRFs
always materializes the entire function result in temporary memory/swap.
Consider something like
pg_dump -t srctab srcdb | psql destdb
instead.
regards, tom lane
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 from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, revoohc@sermonaudio.com
Subject: Re: Copying large tables with DBLink
In-Reply-To: <5020.1111693222@sss.pgh.pa.us>
References: <42430E20.1010600@sermonaudio.com> <5020.1111693222@sss.pgh.pa.us>
* 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