| From: | Daryl Stultz <daryl(dot)stultz(at)opentempo(dot)com> |
|---|---|
| To: | Andreas Kretschmer <andreas(at)a-kretschmer(dot)de>, "pgsql-general(at)postgresql(dot)org" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index |
| Date: | 2017-08-15 19:54:56 |
| Message-ID: | CY4PR1601MB112582A860E34E41E733A1599E8D0@CY4PR1601MB1125.namprd16.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
>>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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andreas Kretschmer | 2017-08-15 20:07:28 | Re: Corrupt index |
| Previous Message | Daryl Stultz | 2017-08-15 19:51:03 | Re: Corrupt index |