Search Postgresql Archives

Re: tstzrange on large table gives poor estimate of expected rows

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: tstzrange on large table gives poor estimate of expected rows
From: Michael Lewis <mlewis@xxxxxxxxxxx>
Date: Mon, 24 Jan 2022 10:43:17 -0700
Cc: pgsql-general General <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <CAGRwtPx_09GnNxsd8J6zfxg=S8Tv4ZG-ezBk7HEex6ROy3czNw@mail.gmail.com>
References: <CAGRwtPx_09GnNxsd8J6zfxg=S8Tv4ZG-ezBk7HEex6ROy3czNw@mail.gmail.com>

If interval_end_date is always 1 day ahead, why store it at all?

Dependencies on a custom stats object wouldn't do anything I don't think because they are offset. They are 100% correlated, but not in a way that any of the existing stat types capture as far as I can figure.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: tstzrange on large table gives poor estimate of expected rows
  - From: Tom Dearman

References:
- tstzrange on large table gives poor estimate of expected rows
  - From: Tom Dearman

Prev by Date: Re: Cannot find hstore operator
Next by Date: Re: Cannot find hstore operator
Previous by thread: tstzrange on large table gives poor estimate of expected rows
Next by thread: Re: tstzrange on large table gives poor estimate of expected rows
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux