| From: | "Paulo Roberto Siqueira" <paulo(dot)siqueira(at)usa(dot)net> |
|---|---|
| To: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Row level locks |
| Date: | 2000-09-24 17:26:30 |
| Message-ID: | NEBBKGEDALIEOOKFKHCLMEBFCDAA.paulo.siqueira@usa.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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 | Tom Lane | 2000-09-24 23:02:25 | Re: [HACKERS] RFC - change of behaviour of pg_get_userbyid & pg_get_viewdef? |
| Previous Message | Philip Warner | 2000-09-24 03:15:55 | RFC - change of behaviour of pg_get_userbyid & pg_get_viewdef? |