public inbox for [email protected]
help / color / mirror / Atom feedPredicate Locking
3+ messages / 3 participants
[nested] [flat]
* Predicate Locking
@ 2006-09-01 17:30 David Fetter <[email protected]>
2006-09-01 22:31 ` Re: Predicate Locking Peter Eisentraut <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: David Fetter @ 2006-09-01 17:30 UTC (permalink / raw)
To: pgsql-docs; PostgreSQL Patches <[email protected]>
Folks,
This patch clarifies the 'predicate locking' section in the docs.
Thanks to Harrison Fisk of MySQL AB for helping.
Cheers,
D
--
David Fetter <[email protected]> http://fetter.org/
phone: +1 415 235 3778 AIM: dfetter666
Skype: davidfetter
Remember to vote!
Index: doc/src/sgml/mvcc.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.57
diff -c -r2.57 mvcc.sgml
*** doc/src/sgml/mvcc.sgml 25 Aug 2006 04:06:45 -0000 2.57
--- doc/src/sgml/mvcc.sgml 1 Sep 2006 17:28:28 -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,480 ----
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. No system based on next-key locking implements it
! either because next-key locking only helps when all your
! predicates are point or range searches against an available
! B-tree index. DB2, however, does implement predicate locking.
</para>
<para>
Attachments:
[text/plain] mvcc_predicate_locking.patch (1.2K, 2-mvcc_predicate_locking.patch)
download | inline diff:
Index: doc/src/sgml/mvcc.sgml
===================================================================
RCS file: /projects/cvsroot/pgsql/doc/src/sgml/mvcc.sgml,v
retrieving revision 2.57
diff -c -r2.57 mvcc.sgml
*** doc/src/sgml/mvcc.sgml 25 Aug 2006 04:06:45 -0000 2.57
--- doc/src/sgml/mvcc.sgml 1 Sep 2006 17:28:28 -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,480 ----
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. No system based on next-key locking implements it
! either because next-key locking only helps when all your
! predicates are point or range searches against an available
! B-tree index. DB2, however, does implement predicate locking.
</para>
<para>
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Predicate Locking
2006-09-01 17:30 Predicate Locking David Fetter <[email protected]>
@ 2006-09-01 22:31 ` Peter Eisentraut <[email protected]>
2006-09-03 01:58 ` Re: Predicate Locking Bruce Momjian <[email protected]>
0 siblings, 1 reply; 3+ messages in thread
From: Peter Eisentraut @ 2006-09-01 22:31 UTC (permalink / raw)
To: pgsql-docs; +Cc: David Fetter <[email protected]>; PostgreSQL Patches <[email protected]>
David Fetter wrote:
> This patch clarifies the 'predicate locking' section in the docs.
What it does it raise the question what "next-key locking is".
I don't think any of this matters for us. We should just remove the
part that claims that no other system implements predicate locking.
--
Peter Eisentraut
http://developer.postgresql.org/~petere/
^ permalink raw reply [nested|flat] 3+ messages in thread
* Re: Predicate Locking
2006-09-01 17:30 Predicate Locking David Fetter <[email protected]>
2006-09-01 22:31 ` Re: Predicate Locking Peter Eisentraut <[email protected]>
@ 2006-09-03 01:58 ` Bruce Momjian <[email protected]>
0 siblings, 0 replies; 3+ messages in thread
From: Bruce Momjian @ 2006-09-03 01:58 UTC (permalink / raw)
To: Peter Eisentraut <[email protected]>; +Cc: pgsql-docs; David Fetter <[email protected]>; PostgreSQL Patches <[email protected]>
Peter Eisentraut wrote:
> David Fetter wrote:
> > This patch clarifies the 'predicate locking' section in the docs.
>
> What it does it raise the question what "next-key locking is".
>
> I don't think any of this matters for us. We should just remove the
> part that claims that no other system implements predicate locking.
OK, new text is:
For these reasons,
<productname>PostgreSQL</productname> does not implement predicate
locking.
--
Bruce Momjian [email protected]
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
^ permalink raw reply [nested|flat] 3+ messages in thread
end of thread, other threads:[~2006-09-03 01:58 UTC | newest]
Thread overview: 3+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2006-09-01 17:30 Predicate Locking David Fetter <[email protected]>
2006-09-01 22:31 ` Peter Eisentraut <[email protected]>
2006-09-03 01:58 ` Bruce Momjian <[email protected]>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox