| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Steven Bradley <sbradley(at)llnl(dot)gov> |
| Cc: | pgsql-interfaces(at)postgreSQL(dot)org |
| Subject: | Re: [INTERFACES] Performance |
| Date: | 1999-06-23 23:30:24 |
| Message-ID: | 22127.930180624@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-interfaces |
Steven Bradley <sbradley(at)llnl(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Kristofer Munn | 1999-06-23 23:31:10 | Perl 5 Interface on 6.5 and lo_creat/lo_open problem |
| Previous Message | Tom Lane | 1999-06-23 23:25:22 | Re: [INTERFACES] pgaccess and RH 6.0? |