From: Kris Jurka <books@ejurka.com>
To: Steve Wampler <swampler@noao.edu>
Cc: Postgres-JDBC <pgsql-jdbc@postgresql.org>
Cc: Postgres-performance <pgsql-performance@postgresql.org>
Subject: Re: [PERFORM] Using a COPY...FROM through JDBC?
Date: Mon, 7 Jun 2004 16:38:01 -0500 (EST)
Message-ID: <Pine.BSO.4.56.0406071636550.6042@leary.csoft.net> (raw)
In-Reply-To: <1086630056.25790.17.camel@weaver.tuc.noao.edu>
References: <1086466349.29063.76.camel@weaver.tuc.noao.edu>
<Pine.BSO.4.56.0406070250280.29634@leary.csoft.net>
<1086630056.25790.17.camel@weaver.tuc.noao.edu>
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients from your mail client; the link fills in
the headers below: reply via email
Some clients, webmail especially, drop In-Reply-To and References from
a link, and the reply then starts a new thread: use the mbox below.
To: pgsql-performance@postgresql.org
Cc: books@ejurka.com, swampler@noao.edu, pgsql-jdbc@postgresql.org
Subject: Re: [PERFORM] Using a COPY...FROM through JDBC?
In-Reply-To: <Pine.BSO.4.56.0406071636550.6042@leary.csoft.net>
References: <1086466349.29063.76.camel@weaver.tuc.noao.edu> <Pine.BSO.4.56.0406070250280.29634@leary.csoft.net> <1086630056.25790.17.camel@weaver.tuc.noao.edu> <Pine.BSO.4.56.0406071636550.6042@leary.csoft.net>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox