Skip site navigation (1) Skip section navigation (2)

Re: (some) Indexes ignored after long-running UPDATE and REINDEX at the same time (8.3.6)

From: Gregory Stark <stark(at)enterprisedb(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Marinos Yannikos <mjy(at)pobox(dot)com>, pgsql-bugs(at)postgresql(dot)org
Subject: Re: (some) Indexes ignored after long-running UPDATE and REINDEX at the same time (8.3.6)
Date: 2009-03-08 17:24:18
Message-ID: 87hc247wsd.fsf@oxford.xeocode.com (view raw or flat)
Thread:
Lists: pgsql-bugs
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> writes:

> Gregory Stark <stark(at)enterprisedb(dot)com> writes:
>> Marinos Yannikos <mjy(at)pobox(dot)com> writes:
>>> I had a strange problem this morning - I started a long-running UPDATE on a
>>> heavily indexed table with about 8m rows last night to test a trigger-based
>>> queue (PgQ):
>
>> I think you were bitten by a gotcha with newly created indexes and "heap-only"
>> updates.
>
> This would only be possible if it were 8.3 and the reindex script used
> REINDEX CONCURRENTLY.  Neither fact is in evidence at this point.

Well it does say "8.3.6" in the subject.

We don't actually support REINDEX CONCURRENTLY... But if my other post is
right then it would still happen (unnecessarily) if the index was originally
built with REINDEX CONCURRENTLY and then reindexed.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com
  Ask me about EnterpriseDB's PostGIS support!

In response to

pgsql-bugs by date

Next:From: Kyle ButtDate: 2009-03-09 14:43:56
Subject: Bug with function returning composite types.
Previous:From: Tom LaneDate: 2009-03-08 16:47:15
Subject: Re: (some) Indexes ignored after long-running UPDATE and REINDEX at the same time (8.3.6)

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group