From: Markus Schaber <schabi@logix-tt.com>
To: ashah <ashah@opuspro.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: Massive Inserts Strategies
Date: Tue, 28 Mar 2006 18:18:44 +0200
Message-ID: <442961E4.3010001@logix-tt.com> (raw)
In-Reply-To: <200603281059.49790.ashah@opuspro.com>
References: <200603221032.10207.ashah@opuspro.com>
<20060322160924.GJ15742@pervasive.com>
<200603281059.49790.ashah@opuspro.com>
Hi, ashah,
ashah wrote:
> I tried this solution, but ran into following problem.
>
> The temp_table has columns (col1, col2, col3).
>
> The original_table has columns (col0, col1, col2, col3)
> Now the extra col0 on the original_table is the unique generated ID by
> the database.
INSERT INTO original_table (col1, col2, col3) SELECT col1, col2, col3
FROM temp_table WHERE ...
HTH,
Markus
--
Markus Schaber | Logical Tracking&Tracing International AG
Dipl. Inf. | Software Development GIS
Fight against software patents in EU! www.ffii.org www.nosoftwarepatents.org
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: schabi@logix-tt.com, ashah@opuspro.com
Subject: Re: Massive Inserts Strategies
In-Reply-To: <442961E4.3010001@logix-tt.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