From: | "Paulo Roberto Siqueira" <paulo(dot)siqueira(at)usa(dot)net> |
---|---|
To: | "PGSQL Admin" <pgsql-admin(at)postgresql(dot)org>, "PGSQL Novice" <pgsql-novice(at)postgresql(dot)org>, <pgsql-general-owner(at)hub(dot)org> |
Subject: | Row level lock |
Date: | 2000-09-26 00:07:38 |
Message-ID: | NEBBKGEDALIEOOKFKHCLGECCCDAA.paulo.siqueira@usa.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin pgsql-novice |
On the documentation
http://www.postgresql.org/users-lounge/docs/7.0/postgres/mvcc4646.htm what
does mean "...Postgres doesn't remember any information about modified rows
in memory and so has no limit to the number of rows locked without lock
escalation."?
Following you find "However, take into account that SELECT FOR UPDATE will
modify selected rows to mark them and so will results in disk writes." Why
does it result in disk writes?
Paulo Siqueira
From | Date | Subject | |
---|---|---|---|
Next Message | vlal | 2000-09-26 07:10:43 | Fail initdb en PostgreSQL V 7.02 |
Previous Message | Loïc TREGOUËT | 2000-09-22 08:03:51 | system tables and indexes problem |
From | Date | Subject | |
---|---|---|---|
Next Message | Chau, Artemis | 2000-09-26 18:26:17 | trigger to run external script |
Previous Message | Oliver_Hall | 2000-09-25 12:43:29 | Re: Case (in)sensitive |