Re: SELECT query results are different depending on whether table statistics are available.

From: James Brauman <james(dot)brauman(at)envato(dot)com>
To: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
Cc: "pgsql-generallists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org>
Subject: Re: SELECT query results are different depending on whether table statistics are available.
Date: 2020-05-28 03:32:22
Message-ID: CAFCW2QPAyPXsEUEzLM6biQsNxLKxGP0qVHAGeZMvkabTFcA4HA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Thanks for the help David, the query was missing a column in a
PARTITION BY expression.

On Thu, May 28, 2020 at 1:14 PM David G. Johnston
<david(dot)g(dot)johnston(at)gmail(dot)com> wrote:
>
> On Wed, May 27, 2020 at 8:09 PM James Brauman <james(dot)brauman(at)envato(dot)com> wrote:
>>
>> -- Run select query (involving several CTEs).
>> SELECT ...;
>>
>> I haven't generated a minimal test case yet, but I did notice that if
>> all CTEs in the SELECT query are defined using AS NOT MATERIALIZED the
>> results are always the same regardless of whether the table has been
>> ANALYZED yet.
>>
>> Could anyone share knowledge about why this is happening?
>
>
> A likely scenario is you are missing an ORDER BY in a location where you are depending on deterministic row ordering and its changing out from underneath you.
>
> David J.
>

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Laurenz Albe 2020-05-28 06:47:53 Re: Can't remove default permissions entry
Previous Message David G. Johnston 2020-05-28 03:13:47 Re: SELECT query results are different depending on whether table statistics are available.