public inbox for [email protected]  
help / color / mirror / Atom feed
From: Alexey Ermakov <[email protected]>
To: Merlin Moncure <[email protected]>
To: [email protected]
Subject: Re: postgres chooses objectively wrong index
Date: Wed, 18 Mar 2026 04:16:30 +0600
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAHyXU0xkTBW4p2N9QNLwye3O5SgzSGSMiPjFb7P8MyXCrEhhwg@mail.gmail.com>
References: <CAHyXU0xkTBW4p2N9QNLwye3O5SgzSGSMiPjFb7P8MyXCrEhhwg@mail.gmail.com>

On 2026-03-18 03:01, Merlin Moncure wrote:
> I've been maintaining an airflow style orchestrator in pl/pgsql, and 
> it's revealed a performance issue I just can't solve.  There is a 
> table, task, which may normally contain billions of rows, but only a 
> tiny portion is interesting for specific reasons—a common pattern in 
> task-type systems.
>
> ...
>
> I'm wondering if there are other tricks that might apply here, for 
> example, multi column index statistics...curious if anyone has 
> thoughts on that.
>
> Any suggestions?
>
> merlin
>
Hello. I think planner doesn't have information about distribution of 
*async.task_execution_state(task)* unless it's part of any full index. I 
would try to give that with extended statistics (postgresql 14+):

create statistics (mcv) task_task_execution_state_stat on ((async.task_execution_state(task))) from async.task;
analyze async.task;

If that won't help - please show distribution from pg_stats_ext view for 
extended statistic above.


--
Alexey Ermakov


view thread (12+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected]
  Subject: Re: postgres chooses objectively wrong index
  In-Reply-To: <[email protected]>

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

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