| From: | Kris Jurka <books(at)ejurka(dot)com> |
|---|---|
| To: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
| Cc: | Thomas Kellerer <spam_eater(at)gmx(dot)net>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: performance for high-volume log insertion |
| Date: | 2009-04-27 06:45:08 |
| Message-ID: | 49F55474.9030909@ejurka.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Scott Marlowe wrote:
> On Sun, Apr 26, 2009 at 11:07 AM, Kris Jurka <books(at)ejurka(dot)com> wrote:
>>
>> As a note for non-JDBC users, the JDBC driver's batch interface allows
>> executing multiple statements in a single network roundtrip. This is
>> something you can't get in libpq, so beware of this for comparison's sake..
>
> Really? I thought that executing statements like so:
>
> select * from a;insert ...;delete;
>
> in psql / libpq would execute them all in one trip.
Right, but those aren't prepared. I suppose it's possible to issue a
prepare and then issue a batch of comma separated "execute" statements,
but that's not exactly a natural interface.
Kris Jurka
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Marlowe | 2009-04-27 07:07:03 | Re: performance for high-volume log insertion |
| Previous Message | Scott Marlowe | 2009-04-27 06:29:19 | Re: performance for high-volume log insertion |