| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> |
| Cc: | Jules Bean <jules(at)jellybean(dot)co(dot)uk>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Performance on inserts |
| Date: | 2000-08-26 15:45:48 |
| Message-ID: | 2963.967304748@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matthew Kirkwood <matthew(at)hairy(dot)beasts(dot)org> writes:
> One of MySQL's little syntax abuses allows:
> INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..);
Actually, that's perfectly standard SQL92, just an item we haven't
got round to supporting yet. (Until we do the fabled querytree
restructuring, it seems a lot harder than it is worth.)
COPY FROM stdin is definitely the fastest way of inserting data,
however, since you avoid a ton of parse/plan overhead that way.
Of course you also lose the ability to have column defaults
computed for you, etc ... there's no free lunch ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-26 16:05:28 | Re: Proposal for supporting outer joins in 7.1 |
| Previous Message | Dominic J. Eidson | 2000-08-26 15:39:55 | Re: Access PostgreSQL server via SSL/Internet |