From: | "Josh Berkus" <josh(at)agliodbs(dot)com> |
---|---|
To: | pgsql-novice(at)postgresql(dot)org |
Subject: | Re: The mystery of concurrent access |
Date: | 2001-10-05 20:26:58 |
Message-ID: | web-142736@davinci.ethosmedia.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-novice |
P.V.,
> When 2 processes/people are simultaneously working on a table
>
> * does Postgres automatically enforce some sort of locking?
> * do the changes made by process A become visible to process B
> immediately
> (of course, the result of a SELECT wouldn't change dynamically, but
> suppose
> process B did another SELECT, would it access process A's records?)
Please read:
http://www.postgresql.org/idocs/index.php?mvcc.html
-Josh
______AGLIO DATABASE SOLUTIONS___________________________
Josh Berkus
Complete information technology josh(at)agliodbs(dot)com
and data management solutions (415) 565-7293
for law firms, small businesses fax 621-2533
and non-profit organizations. San Francisco
Attachment | Content-Type | Size |
---|---|---|
unknown_filename | text/plain | 2 bytes |
unknown_filename | text/plain | 2 bytes |
unknown_filename | text/plain | 2 bytes |
From | Date | Subject | |
---|---|---|---|
Next Message | Jason Earl | 2001-10-05 21:52:05 | Re: The mystery of concurrent access |
Previous Message | Tom Lane | 2001-10-05 19:08:34 | Re: How to find out that a record has been updated |