On Tue, May 10, 2016 at 7:41 AM, David Rowley
wrote:
> On 10 May 2016 at 16:34, David G. Johnston
> wrote:
> > On Mon, May 9, 2016 at 8:53 AM, Benedikt Grundmann
> > wrote:
> >>
> >> We just run into a very simple query that the planner does much worse on
> >> than we thought it would (in produ
On 10 May 2016 at 16:34, David G. Johnston wrote:
> On Mon, May 9, 2016 at 8:53 AM, Benedikt Grundmann
> wrote:
>>
>> We just run into a very simple query that the planner does much worse on
>> than we thought it would (in production the table in question is ~ 100 GB).
>> It surprised us given th
On Mon, May 9, 2016 at 8:53 AM, Benedikt Grundmann <
bgrundm...@janestreet.com> wrote:
> We just run into a very simple query that the planner does much worse on
> than we thought it would (in production the table in question is ~ 100
> GB). It surprised us given the planner is generally quite go
We just run into a very simple query that the planner does much worse on
than we thought it would (in production the table in question is ~ 100
GB). It surprised us given the planner is generally quite good, so I
thought I share our surprise
Setup:
postgres_prod@proddb_testing=# select version()