From: | "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
---|---|
To: | <pgsql-patches(at)postgresql(dot)org>, "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Subject: | Re: predicate locking knowledge |
Date: | 2006-03-23 19:16:33 |
Message-ID: | 44229FB1.EE98.0025.0@wicourts.gov |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
>>> On Thu, Mar 23, 2006 at 1:13 pm, in message
<44229EE6(dot)EE98(dot)0025(dot)0(at)wicourts(dot)gov>, "Kevin Grittner"
<Kevin(dot)Grittner(at)wicourts(dot)gov> wrote:
Attachment didn't seem to go through. Embedding below.
Index: mvcc.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.55
diff -c -r2.55 mvcc.sgml
*** mvcc.sgml 10 Mar 2006 19:10:48 -0000 2.55
--- mvcc.sgml 23 Mar 2006 18:58:13 -0000
***************
*** 471,477 ****
result in problems. (Certainly the example above is rather
contrived
and unlikely to represent real software.) Accordingly,
<productname>PostgreSQL</productname> does not implement
predicate
! locking, and so far as we are aware no other production DBMS does
either.
</para>
<para>
--- 471,477 ----
result in problems. (Certainly the example above is rather
contrived
and unlikely to represent real software.) Accordingly,
<productname>PostgreSQL</productname> does not implement
predicate
! locking.
</para>
<para>
From | Date | Subject | |
---|---|---|---|
Next Message | Mark Wong | 2006-03-23 19:27:45 | Re: WIP: splitting BLCKSZ |
Previous Message | Kevin Grittner | 2006-03-23 19:13:10 | predicate locking knowledge |