pg.ddx.io  pgsql-sql@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Herouth Maoz <herouth@oumail.openu.ac.il>
To: G. Anthony Reina <reina@nsi.edu>
Cc: pgsql-general@postgreSQL.org
Subject: Re: [SQL] Reading and writing at the same time
Date: Sun, 25 Oct 1998 11:49:03 +0200
Message-ID: <l03110701b258a3995c0e@[147.233.159.109]> (raw)
In-Reply-To: <3630D1A0.BBCD1F46@nsi.edu>

(Redirected from SQL list to GENERAL list)

At 20:57 +0200 on 23/10/98, G. Anthony Reina wrote:

> I know that Postgres has table-level locking so that once a write is
> being performed on a table, no other reads or writes can be performed
> until that write finishes.
>
> I have a C program that performs several updates and inserts to a table.
> I found that I am able, despite any table locking, to use the front-end
> psql program at the same time to select data from the same table that is
> being written to. So in essence, I am able to have one program that is
> writing while at the same time another program reads (without running
> into aborted backends).

Are you sure you interpret what you see correctly? The backend in fact
locks out any readers while updates take place. I have a hunch that you did
not declare a transaction in your C program, and thus, each of the updates
ani inserts in it is a separate transaction.

When that happens, the reads (from your psql frontend) and the writes (from
your C) are interspersed, because the lock only holds while a transaction
is active. The next update in your C program may wait until the read in
PSQL has been done.

Herouth

--
Herouth Maoz, Internet developer.
Open University of Israel - Telem project
http://telem.openu.ac.il/~herutma





view thread (2+ messages)

Message-ID: <l03110701b258a3995c0e@[147.233.159.109]>
Permalink:  ../l03110701b258a3995c0e@%5B147.233.159.109%5D/
Also on:    postgresql.org/message-id/l03110701b258a3995c0e@[147.233.159.109]

 · 

reply

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-sql@postgresql.org
  Cc: herouth@oumail.openu.ac.il, reina@nsi.edu, pgsql-general@postgreSQL.org
  Subject: Re: [SQL] Reading and writing at the same time
  In-Reply-To: <l03110701b258a3995c0e@[147.233.159.109]>
  References: <3630D1A0.BBCD1F46@nsi.edu> <l03110701b258a3995c0e@[147.233.159.109]>

* 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