From: | "G(dot) Anthony Reina" <reina(at)nsi(dot)edu> |
---|---|
To: | reina(at)nsi(dot)edu, "pgsql-questions(at)postgresql(dot)org" <pgsql-sql(at)postgreSQL(dot)org> |
Subject: | Reading and writing at the same time |
Date: | 1998-10-23 18:57:36 |
Message-ID: | 3630D1A0.BBCD1F46@nsi.edu |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-sql |
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).
So with table-level locking, does the postmaster completely abort any
backends that make a request while a write is being done; or, does the
postmaster simply tell the other backends to hold for a few seconds
until the write is completed and then let the new backend process?
-Tony Reina
From | Date | Subject | |
---|---|---|---|
Next Message | Moises Flores | 1998-10-24 19:24:47 | i need information for prostgress sql |
Previous Message | Taral | 1998-10-23 17:57:13 | RE: [GENERAL] date null |
From | Date | Subject | |
---|---|---|---|
Next Message | Leslie Mikesell | 1998-10-24 17:37:42 | varchar vs. text |
Previous Message | ronggui | 1998-10-22 13:05:47 | Help me ,Thank you !! |