pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Ancoron Luciferis <ancoron.luciferis@googlemail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Custom opclass for column statistics?
Date: Sat, 06 Jul 2019 09:58:58 -0400
Message-ID: <26689.1562421538@sss.pgh.pa.us> (raw)
In-Reply-To: <b0590dd1-5bfb-ad62-c4d0-a7057c04a68b@googlemail.com>
References: <b0590dd1-5bfb-ad62-c4d0-a7057c04a68b@googlemail.com>

Ancoron Luciferis <ancoron.luciferis@googlemail.com> writes:
> I've been wondering whether it is possible somehow to have the standard
> column statistics to respect a certain operator class?

In principle, pg_statistic can represent stats for a non-default opclass.
Teaching ANALYZE to collect such stats when appropriate, and then teaching
the planner to use them when appropriate, is left as an exercise for the
reader.

I think the "when appropriate" bit is actually the hardest part of that.
Possibly, if you were satisfied with a relatively manual approach,
you could proceed by using CREATE STATISTICS to declare interest in
keeping standard stats for a non-default sort order.  Not sure what to
do if you want it to be automatic, because I don't think people would
hold still for having ANALYZE collect stats for any random non-default
opclass automatically.  Maybe a new opclass property?

			regards, tom lane





view thread (7+ messages)  latest in thread

Message-ID: <26689.1562421538@sss.pgh.pa.us>
Permalink:  ../26689.1562421538@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/26689.1562421538@sss.pgh.pa.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: tgl@sss.pgh.pa.us, ancoron.luciferis@googlemail.com, pgsql-performance@lists.postgresql.org
  Subject: Re: Custom opclass for column statistics?
  In-Reply-To: <26689.1562421538@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox