From: ctrl@altonsys.com
To: pgsql-sql@postgresql.org
Subject: Re: best method to copy data across databases
Date: 3 Jul 2004 11:19:50 -0700
Message-ID: <46a31c4d.0407031019.78b04fdb@posting.google.com> (raw)
References: <46a31c4d.0407011942.37839bb0@posting.google.com>
<272e4be7.0407020310.18785557@posting.google.com>
<14059.1088777527@sss.pgh.pa.us>
Many thanks Tony and Tom,
since this was a "one time" process speed wasn't an issue...
I just did a plain pg_dump with insert and explicit column names in
the dump, then used vi to rename the columns and get rid of some of
them...
non very scientific but it worked :)
cheers.
tgl@sss.pgh.pa.us (Tom Lane) wrote in message news:<14059.1088777527@sss.pgh.pa.us>...
> reina_ga@hotmail.com (Tony Reina) writes:
> > If the 2 tables have different arrangements, then I'm not sure if
> > there is a quick way. The safest way is probably to do a pg_dump
> > --attribute-inserts.
>
> In recent versions (definitely 7.4, don't remember about 7.3),
> pg_dump will include a column list in its COPY commands, so a
> plain pg_dump should work. The way with COPY will be a good bit
> faster than a pile of INSERT commands.
>
> regards, tom lane
>
> ---------------------------(end of broadcast)---------------------------
> TIP 9: the planner will ignore your desire to choose an index scan if your
> joining column's datatypes do not match
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-sql@postgresql.org
Cc: ctrl@altonsys.com
Subject: Re: best method to copy data across databases
In-Reply-To: <46a31c4d.0407031019.78b04fdb@posting.google.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