From: | Jeff MacDonald <jeff(at)pgsql(dot)com> |
---|---|
To: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Locking |
Date: | 2000-03-01 18:10:22 |
Message-ID: | Pine.BSF.4.10.10003011409380.5539-100000@rage.hub.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Hi folks,
I posted this on docs and didn't get a reply, so i'm throwing it in here.
======================
Hi,
I was reading the MVCC docs and came across this statement
"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. "
And this is how i interpreted it.
you can have unlimited rows locked with out it going to a 'table
lock'
Do these two staements say the samething ?
Jeff MacDonald
jeff(at)pgsql(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2000-03-01 18:35:44 | Re: BIT/BIT VARYING names (was Re: [HACKERS] Beta for 4:30AST) |
Previous Message | Tom Lane | 2000-03-01 17:50:12 | Re: [HACKERS] having and union in v7beta |