| From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
|---|---|
| To: | Aaron Pelz <aaronepelz(at)gmail(dot)com> |
| Cc: | pgsql-general General <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: Corrupt index stopping autovacuum system wide |
| Date: | 2019-07-18 16:21:23 |
| Message-ID: | CAH2-WzksZTcAChogQCfrDeqbHCBZC3iBA8+WCcNp5NodrKnOaw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On Thu, Jul 18, 2019 at 9:06 AM Aaron Pelz <aaronepelz(at)gmail(dot)com> wrote:
> It's a simple btree expression on a geometry(Point,4326) , no expression no partial no composite.
The cause of the corruption may be a bug in a Postgis B-Tree operator
class. I reported a bug in the Geography type that could lead to
corrupt B-Tree indexes (not Geometry):
https://trac.osgeo.org/postgis/ticket/3841
Though I also see what could be a comparable bug in Geometry:
https://trac.osgeo.org/postgis/ticket/3777
These bugs are from about 3 years ago. If I'm right you should be able
to isolate the bug using amcheck.
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2019-07-18 17:01:22 | Re: PostgreSQL as a Service |
| Previous Message | Aaron Pelz | 2019-07-18 16:06:43 | Re: Corrupt index stopping autovacuum system wide |