From: | Kris Jurka <books(at)ejurka(dot)com> |
---|---|
To: | Steve Wampler <swampler(at)noao(dot)edu> |
Cc: | Postgres-JDBC <pgsql-jdbc(at)postgresql(dot)org>, Postgres-performance <pgsql-performance(at)postgresql(dot)org> |
Subject: | Re: [PERFORM] Using a COPY...FROM through JDBC? |
Date: | 2004-06-07 21:38:01 |
Message-ID: | Pine.BSO.4.56.0406071636550.6042@leary.csoft.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-jdbc pgsql-performance |
On Mon, 7 Jun 2004, Steve Wampler wrote:
> I do have a little concern about what's happening in the
> back end during the copy - I suspect the entire table is
> locked, which may impact the performance when multiple
> clients are saving entries into the table. Anyone know
> if that's how COPY works? (For that matter, would that
> also be true of a transaction consisting of a set of
> inserts?)
>
The table is not locked in either the copy or the insert case.
Kris Jurka
From | Date | Subject | |
---|---|---|---|
Next Message | Brian G. Huber | 2004-06-08 15:16:01 | Cursor returned from procedure ignores setFetchSize() on CallableStatement |
Previous Message | Steve Wampler | 2004-06-07 17:59:25 | Re: [PERFORM] Using a COPY...FROM through JDBC? |
From | Date | Subject | |
---|---|---|---|
Next Message | borajetta | 2004-06-07 21:47:17 | 50 000 000 Table entries and I have to do a keyword search HELP NEEDED |
Previous Message | Dan Langille | 2004-06-07 21:02:36 | Re: seq scan woes |