| From: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org,Daryl Stultz <daryl(dot)stultz(at)opentempo(dot)com>,"pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index |
| Date: | 2017-08-15 20:07:28 |
| Message-ID: | D056F14D-B32E-4AD8-8F3B-ADC78F694BD3@a-kretschmer.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 15 August 2017 21:54:56 GMT+02:00, Daryl Stultz <daryl(dot)stultz(at)opentempo(dot)com> wrote:
>
>>>We are using PostgreSQL 9.3.14 on a managed Amazon RDS with a
>
>
>>Are you using reindex concurrently? There was a bugfix in 9.3.16 (+-1,
>i'm not sure).
>
>Hi Andreas, not that I'm aware of. I issue "reindex table mytable" to
>get out of the bad situation. I'm not sure if you are saying this bug
>could be getting me into the situation. If you don't mean that I am
>manually executing reindex concurrently, how do I go about determining
>if the system is using that procedure? Perhaps after some transaction,
>the system rebuilds the index automatically using "concurrently" and
>that is buggy/failing?
>
>Thanks.
>
>/Daryl
I only wanted to exclude it. Anyway, you should install the latest patches.
Regards, Andreas.
--
2ndQuadrant - The PostgreSQL Support Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John R Pierce | 2017-08-15 21:02:58 | Re: Corrupt index |
| Previous Message | Daryl Stultz | 2017-08-15 19:54:56 | Re: Corrupt index |