| From: | Chris <chrisb(at)nimrod(dot)itg(dot)telstra(dot)com(dot)au> |
|---|---|
| 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-27 23:11:49 |
| Message-ID: | 39A9A035.75EF299F@nimrod.itg.telecom.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Matthew Kirkwood wrote:
>
> On Sat, 26 Aug 2000, Jules Bean wrote:
>
> > Is there any simple way for Pg to combine inserts into one bulk?
> > Specifically, their effect on the index files. It has always seemed
> > to me to be one of the (many) glaring flaws in SQL that the INSERT
> > statement only takes one row at a time.
>
> One of MySQL's little syntax abuses allows:
>
> INSERT INTO tab (col1, ..) VALUES (val1, ..), (val2, ..);
Wouldn't....
INSERT INTO tab (col1, ..); INSERT INTO tab VALUES (val1, ..); INSERT
INTO tab (val2, ..);
also avoid a database round trip??
| From | Date | Subject | |
|---|---|---|---|
| Next Message | The Hermit Hacker | 2000-08-27 23:31:43 | Re: Too many open files (was Re: spinlock problems reported earlier) |
| Previous Message | Chris | 2000-08-27 22:53:09 | Re: [HACKERS] Pure ODBMS (fwd) |