From: | Greg Smith <greg(at)2ndquadrant(dot)com> |
---|---|
To: | Kevin Grittner <Kevin(dot)Grittner(at)wicourts(dot)gov> |
Cc: | Dan Ports <drkp(at)csail(dot)mit(dot)edu>, Vlad Arkhipov <arhipov(at)dc(dot)baikal(dot)ru>, pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Predicate locking |
Date: | 2011-05-04 02:36:13 |
Message-ID: | 4DC0BB9D.6040903@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Kevin Grittner wrote:
>> I don't think Vlad is being unreasonable here; he's provided a
>> test case demonstrating the behavior he'd like to see, and shown
>> it doesn't work as expected.
>>
>
> ... on a toy table with contrived values. How different is this
> from the often-asked question about why a query against a four-line
> table is not using the index they expect, and how can we expect it
> to scale if it doesn't?
It's not, but in that case I've been known to show someone that the
behavior they're seeing doesn't happen on a larger table. My point was
just that no one has really done that here yet: provided an example
showing SSI serialization working as a substitute for predicate locking
in this sort of use case. I trust that the theory is sound here, and
yet I'd still like to see that demonstrated. This is why I launched
into making a less trivial test case.
--
Greg Smith 2ndQuadrant US greg(at)2ndQuadrant(dot)com Baltimore, MD
PostgreSQL Training, Services, and 24x7 Support www.2ndQuadrant.us
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-05-04 02:47:34 | Re: adding a new column in IDENTIFY_SYSTEM |
Previous Message | Tom Lane | 2011-05-04 02:28:05 | Re: Extreme bloating of intarray GiST indexes |