Postgres Pro
Downloads
Home   >   mailing lists

Re: SELECT query results are different depending on whether tablestatistics are available. - Mailing list pgsql-general

From David G. Johnston
Subject Re: SELECT query results are different depending on whether tablestatistics are available.
Date
Msg-id CAKFQuwZuJfDTD5bnEpNj3Bpd6E2pdMF9jfUVBim+gp_ALmH7Eg@mail.gmail.com
Whole thread Raw
In response to SELECT query results are different depending on whether tablestatistics are available.  (James Brauman <james.brauman@envato.com>)
Responses Re: SELECT query results are different depending on whether tablestatistics are available.  (James Brauman <james.brauman@envato.com>)
List pgsql-general
Tree view
On Wed, May 27, 2020 at 8:09 PM James Brauman <james.brauman@envato.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.

pgsql-general by date:

Previous
From: James Brauman
Date:
Subject: SELECT query results are different depending on whether tablestatistics are available.
Next
From: James Brauman
Date:
Subject: Re: SELECT query results are different depending on whether tablestatistics are available.