Skip site navigation (1) Skip section navigation (2)

Re: [PERFORM] Using a COPY...FROM through JDBC?

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 (view raw or flat)
Thread:
Lists: pgsql-jdbcpgsql-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

In response to

pgsql-performance by date

Next:From: borajettaDate: 2004-06-07 21:47:17
Subject: 50 000 000 Table entries and I have to do a keyword search HELP NEEDED
Previous:From: Dan LangilleDate: 2004-06-07 21:02:36
Subject: Re: seq scan woes

pgsql-jdbc by date

Next:From: Brian G. HuberDate: 2004-06-08 15:16:01
Subject: Cursor returned from procedure ignores setFetchSize() on CallableStatement
Previous:From: Steve WamplerDate: 2004-06-07 17:59:25
Subject: Re: [PERFORM] Using a COPY...FROM through JDBC?

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group