On 28 May 2009, at 01:51, "Kevin Grittner"
> At the point where we added an escalation
> to table locking for the limit, started with the table lock when we
> knew it was a table scan, and locked the index range for an index
I still think you're stuck in the mssql/sybase mode of thought here.
Postgres supports a whole lot more scan types than just these two and
many of them use multiple indexes or indexes that don't correspond to
ranges of key values at all.
I think you have to forget about any connection between predicates and
either indexes or scan types. You need a way to represent predicates
which can be stored and looked up independently of any indexes.
Without any real way to represent predicates this is all pie in the
sky. The reason we don't have predicate locking is because of this
problem which it sounds like we're no closer to solving.
In response to
pgsql-hackers by date
|Next:||From: Greg Stark||Date: 2009-05-28 01:37:20|
|Subject: Re: survey of WAL blocksize changes|
|Previous:||From: Robert Haas||Date: 2009-05-28 01:29:11|
|Subject: Re: PostgreSQL Developer meeting minutes up|