Re: Use of additional index columns in rows filtering - Mailing list pgsql-hackers

From Jeff Davis
Subject Re: Use of additional index columns in rows filtering
Date
Msg-id 4ed17d03bee6fffdab865a7161c5a9a6947f4304.camel@j-davis.com
Whole thread Raw
In response to Re: Use of additional index columns in rows filtering  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: Use of additional index columns in rows filtering
List pgsql-hackers
On Sun, 2023-07-23 at 14:04 +0200, Tomas Vondra wrote:
> But I'm getting a bit lost regarding what's the proposed costing
> strategy. It's hard to follow threads spanning days, with various
> other
> distractions, etc.

I'm getting a bit lost in this discussion as well -- for the purposes
of this feature, we only need to know whether to push down a clause as
an Index Filter or not, right?

Could we start out conservatively and push down as an Index Filter
unless there is some other clause ahead of it that can't be pushed
down? That would allow users to have some control by writing clauses in
the desired order or wrapping them in functions with a declared cost.

Regards,
    Jeff Davis




pgsql-hackers by date:

Previous
From: Pierre Ducroquet
Date:
Subject: Re: Inefficiency in parallel pg_restore with many tables
Next
From: Tom Lane
Date:
Subject: Re: psql not responding to SIGINT upon db reconnection