From: Tom Lane <tgl@sss.pgh.pa.us>
To: jellej@pacbell.net
Cc: pgsql-performance@postgresql.org
Subject: Re: Questions about 2 databases.
Date: Fri, 11 Mar 2005 15:33:42 -0500
Message-ID: <5055.1110573222@sss.pgh.pa.us> (raw)
In-Reply-To: <Pine.LNX.4.61.0503110945070.24097@localhost.localdomain>
References: <6.2.0.14.0.20050311155221.041aa528@pop.interactivemediafactory.net>
<Pine.LNX.4.61.0503110945070.24097@localhost.localdomain>
jelle <jellej@pacbell.net> writes:
> 1) on a single 7.4.6 postgres instance does each database have it own WAL
> file or is that shared? Is it the same on 8.0.x?
Shared.
> 2) what's the high performance way of moving 200 rows between similar
> tables on different databases? Does it matter if the databases are
> on the same or seperate postgres instances?
COPY would be my recommendation. For a no-programming-effort solution
you could just pipe the output of pg_dump --data-only -t mytable
into psql. Not sure if it's worth developing a custom application to
replace that.
> My web app does lots of inserts that aren't read until a session is
> complete. The plan is to put the heavy insert session onto a ramdisk based
> pg-db and transfer the relevant data to the master pg-db upon session
> completion. Currently running 7.4.6.
Unless you have a large proportion of sessions that are abandoned and
hence never need be transferred to the main database at all, this seems
like a dead waste of effort :-(. The work to put the data into the main
database isn't lessened at all; you've just added extra work to manage
the buffer database.
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 using the --to and --cc options:
reply via email
To: pgsql-performance@postgresql.org
Cc: tgl@sss.pgh.pa.us, jellej@pacbell.net
Subject: Re: Questions about 2 databases.
In-Reply-To: <5055.1110573222@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