| From: | Mike Mascari <mascarm(at)mascari(dot)com> |
|---|---|
| To: | Chris Bowlby <chris(at)pgsql(dot)com> |
| Cc: | simon(at)2ndquadrant(dot)com, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: lock related issues... |
| Date: | 2004-01-29 03:27:05 |
| Message-ID: | 40187D89.4040000@mascari.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Chris Bowlby wrote:
> Hi Simon,
>
> Thanks for the confirmation, I just wanted to make sure I was not
> going ape over it and getting confused.
>
> At 08:04 PM 1/28/04, Simon Riggs wrote:
>
>> >Chris Bowlby writes
>> > I'm looking for some details on how the locking system works in
>> > relation to transactions dealing with INSERTs and UPDATEs. The version
>> > of PostgreSQL is 7.3.2
>>
>> p.152 of the 7.3.2 Users Guide, section 9.2.1 Read Committed Isolation
>> Level applies to your situation as described
>
A great description of concurrency issues is Tom Lane's O'Reilly
presentation. After installing PostgreSQL, a message should be output to
read it:
http://conferences.oreillynet.com/presentations/os2002/lane_tom.tar.gz
Mike Mascari
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tatsuo Ishii | 2004-01-29 04:44:59 | rule and JDBC |
| Previous Message | Chris Bowlby | 2004-01-29 00:53:08 | Re: lock related issues... |