Re: Problems with "pg.dropped" column after upgrade 9.5 to 9.6

From: Michael Paquier <michael(dot)paquier(at)gmail(dot)com>
To: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
Cc: Pavel Hanák <hanak(at)is-it(dot)eu>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: Problems with "pg.dropped" column after upgrade 9.5 to 9.6
Date: 2016-11-02 07:46:46
Message-ID: CAB7nPqQ7zjN78nWvFfG7tk0DdtMvPnR9_+xA68F4nwpRiStnaw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Wed, Nov 2, 2016 at 3:54 PM, Michael Paquier
<michael(dot)paquier(at)gmail(dot)com> wrote:
> I am just digging into it... An interesting part is that removing the
> WHERE clause makes the regression go away.

And one bisect later:
commit: 3fc6e2d7f5b652b417fa6937c34de2438d60fa9f
author: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
date: Mon, 7 Mar 2016 15:58:22 -0500
Make the upper part of the planner work by generating and comparing Paths

In short, that's going to be fun to create a patch...
--
Michael

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message lello. ds 2016-11-02 08:49:12 Visual VC++ runtime error
Previous Message Michael Paquier 2016-11-02 06:54:21 Re: Problems with "pg.dropped" column after upgrade 9.5 to 9.6