| From: | Peter Geoghegan <pg(at)heroku(dot)com> |
|---|---|
| To: | Ian Barwick <ian(at)2ndquadrant(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possible index issue on 9.5 slave |
| Date: | 2014-06-19 02:58:48 |
| Message-ID: | CAM3SWZSNfnNKCsFF5jFbZXuXrk8tKNdHMM+75J5P9bUNXPHi_Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jun 18, 2014 at 6:54 PM, Ian Barwick <ian(at)2ndquadrant(dot)com> wrote:
> I've just run into an index issue on 9.5 HEAD on a slave (master and slave
> both compiled from 66802246e22d51858cd543877fcfddf24e6812f2); details
> below (I have only found one index on the slave where the issue occurs so far).
Would you mind running my btreecheck tool on both systems? That might
shed some light on this. You can get it from:
http://www.postgresql.org/message-id/CAM3SWZRtV+xmRWLWq6c-x7czvwavFdwFi4St1zz4dDgFH4yN4g@mail.gmail.com
.
I suggest running bt_parent_index_verify() and bt_leftright_verify()
on all indexes on both systems. It shouldn't take too long.
Thanks
--
Peter Geoghegan
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2014-06-19 03:04:39 | Re: [bug fix] Memory leak in dblink |
| Previous Message | David Fetter | 2014-06-19 02:49:00 | Re: delta relations in AFTER triggers |