On 22 March 2014 16:28, Jim Nasby wrote:
> On 3/21/14, 7:59 PM, Vik Fearing wrote:
>>
>> On 03/22/2014 01:43 AM, Thom Brown wrote:
>>>
>>> Hi,
>>>
>>> I've created a table with 1000 partial indexes. Each one matches
>>> exactly one row based on the predicate WHERE id = .
>>>
>>> However, when I p
On 3/21/14, 7:59 PM, Vik Fearing wrote:
On 03/22/2014 01:43 AM, Thom Brown wrote:
Hi,
I've created a table with 1000 partial indexes. Each one matches
exactly one row based on the predicate WHERE id = .
However, when I perform an UPDATE of a single row in a transaction,
I've noticed that all
On 22 March 2014 15:04, Tom Lane wrote:
> Thom Brown writes:
>> On 22 March 2014 05:32, Tom Lane wrote:
>>> Yes. You can't determine whether the index needs to get a new entry
>>> without examining its metadata, and that's what the lock is mainly about.
>
>> I see. Why does this apply to delet
Thom Brown writes:
> On 22 March 2014 05:32, Tom Lane wrote:
>> Yes. You can't determine whether the index needs to get a new entry
>> without examining its metadata, and that's what the lock is mainly about.
> I see. Why does this apply to deletes too?
The executor doesn't take locks on inde
On 22 March 2014 05:32, Tom Lane wrote:
> Thom Brown writes:
>> Is it necessary for a partial index that doesn't include the row to be
>> involved in locking?
>
> Yes. You can't determine whether the index needs to get a new entry
> without examining its metadata, and that's what the lock is mai
Thom Brown writes:
> Is it necessary for a partial index that doesn't include the row to be
> involved in locking?
Yes. You can't determine whether the index needs to get a new entry
without examining its metadata, and that's what the lock is mainly about.
The only possible alternative would be
On 22 March 2014 00:59, Vik Fearing wrote:
> On 03/22/2014 01:43 AM, Thom Brown wrote:
>> Hi,
>>
>> I've created a table with 1000 partial indexes. Each one matches
>> exactly one row based on the predicate WHERE id = .
>>
>> However, when I perform an UPDATE of a single row in a transaction,
>>
On 03/22/2014 01:43 AM, Thom Brown wrote:
> Hi,
>
> I've created a table with 1000 partial indexes. Each one matches
> exactly one row based on the predicate WHERE id = .
>
> However, when I perform an UPDATE of a single row in a transaction,
> I've noticed that all those partial indexes show up i
Hi,
I've created a table with 1000 partial indexes. Each one matches
exactly one row based on the predicate WHERE id = .
However, when I perform an UPDATE of a single row in a transaction,
I've noticed that all those partial indexes show up in pg_locks with
RowExclusiveLock.
Only 2 of those ind
