| From: | Ian Barwick <ian(at)2ndquadrant(dot)com> |
|---|---|
| To: | Peter Geoghegan <pg(at)heroku(dot)com> |
| Cc: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Possible index issue on 9.5 slave |
| Date: | 2014-06-19 03:09:22 |
| Message-ID: | 53A25462.2000208@2ndquadrant.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 19/06/14 11:58, Peter Geoghegan wrote:
> 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.
Interesting, I'll take a look later.
Thanks
Ian Barwick
--
Ian Barwick http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2014-06-19 03:19:57 | Re: [bug fix] Memory leak in dblink |
| Previous Message | Joe Conway | 2014-06-19 03:04:39 | Re: [bug fix] Memory leak in dblink |