| From: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com> |
|---|---|
| To: | Thom Brown <thom(at)linux(dot)com> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Error with index on unlogged table |
| Date: | 2015-03-25 02:38:30 |
| Message-ID: | CAB7nPqR7H-B0BoKQNwGyJK0hPo3HZ0HFfQoLED=iYE2ouJHiyQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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...
--
Michael
| Attachment | Content-Type | Size |
|---|---|---|
| 20150325_reindex_index_fix.patch | application/x-patch | 885 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-03-25 03:11:26 | Re: Replication identifiers, take 4 |
| Previous Message | Bruce Momjian | 2015-03-25 02:35:10 | Re: pgsql: btree_gin: properly call DirectFunctionCall1() |