Re: Error with index on unlogged table - Mailing list pgsql-hackers

From Amit Langote
Subject Re: Error with index on unlogged table
Date
Msg-id CA+HiwqG6jQuFP-k6K1BVApURn8KdV+s9nLy067aX_7YWrVn+Hg@mail.gmail.com
Whole thread Raw
In response to Re: Error with index on unlogged table  (Thom Brown <thom@linux.com>)
List pgsql-hackers


On Wednesday, March 25, 2015, Thom Brown <thom@linux.com> wrote:
On 25 March 2015 at 12:22, Amit Langote <amitlangote09@gmail.com> wrote:
On Wednesday, March 25, 2015, Michael Paquier <michael.paquier@gmail.com> wrote:
>
> On Tue, Mar 24, 2015 at 8:46 PM, Thom Brown wrote:
> > The index is unlogged until reindexing...
> >
> > [...]
> > Which is think also raises the question, why are unlogged indexes made
> > persistent by a reindex?
>
> That's a bug of HEAD, ~9.4 keeping the index as unlogged even after
> REINDEX INDEX. What happens is that ReindexIndex relies on
> relpersistence provided by makeRangeVar at parse time, which is just
> incorrect as it uses RELPERSISTENCE_PERMANENT all the time. The patch
> attached fixes that...
>

How about VACUUM FULL and CLUSTER as the problem seems to have been
reported to be there too?

No, those are okay.  They actually revert the index back to the same persistence level as the table they're attached to. 

Ah, I misread then; sorry about the noise.

Amit 

pgsql-hackers by date:

Previous
From: Thom Brown
Date:
Subject: Re: Parallel Seq Scan
Next
From: Andres Freund
Date:
Subject: Re: Error with index on unlogged table