From: Tom Lane <tgl@sss.pgh.pa.us>
To: Steven Bradley <sbradley@llnl.gov>
Cc: pgsql-interfaces@postgreSQL.org
Subject: Re: [INTERFACES] Performance
Date: Wed, 23 Jun 1999 19:30:24 -0400
Message-ID: <22127.930180624@sss.pgh.pa.us> (raw)
In-Reply-To: <3.0.5.32.19990623150509.0092e990@poptop.llnl.gov>
Steven Bradley <sbradley@llnl.gov> writes:
> I wanted to use a prepared SQL statement, but it turns out that Postgres
> runs the query through the parser-planner-executor cycle on each iteration.
> There is no way to prevent this.
> The next thing I though of doing was to "bulk load" several records in one
> INSERT through the use of array processing. Do any of the Postgres
> interfaces support this? (by arrays, I don't mean array columns in the
> table).
If you're just inserting literal data, use COPY FROM STDIN instead of
INSERTs. Much less per-tuple overhead, although it's uglier.
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-interfaces@postgresql.org
Cc: tgl@sss.pgh.pa.us, sbradley@llnl.gov
Subject: Re: [INTERFACES] Performance
In-Reply-To: <22127.930180624@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