Re: cache lookup failed for statistics object 123 - Mailing list pgsql-hackers

From Tomas Vondra
Subject Re: cache lookup failed for statistics object 123
Date
Msg-id 8c78067f-9562-6e78-bf56-b29116e81faf@enterprisedb.com
Whole thread Raw
In response to cache lookup failed for statistics object 123  (Justin Pryzby <pryzby@telsasoft.com>)
Responses Re: cache lookup failed for statistics object 123
List pgsql-hackers
Hi,

On 5/5/21 11:09 PM, Justin Pryzby wrote:
> Per sqlsmith.
> 
> postgres=# SELECT pg_get_statisticsobjdef_expressions(123);
> ERROR:  cache lookup failed for statistics object 123
> postgres=# \errverbose
> ERROR:  XX000: cache lookup failed for statistics object 123
> LOCATION:  pg_get_statisticsobjdef_expressions, ruleutils.c:1762
> 
> The expectation is that sql callable functions should return null rather than
> hitting elog().
> 

Right, thanks for noticing this.

> In the 003 patch, I wonder if this part should be updated, too:
> 
> | ... which can greatly improve query plans that use the expression index.
> 
> It can improve queries even that don't use the index, right ?
 >
> Say, if a query has f(x) = 11, and the MCV list for the expression shows that
> 50% of the table has f(x)=11, then the query might decide to *not* use an index
> scan.

Yeah, it should talk about improving estimates, it's mostly unrelated to 
using indexes.

regards



pgsql-hackers by date:

Previous
From: Andreas Seltenreich
Date:
Subject: Re: Multiple hosts in connection string failed to failover in non-hot standby mode
Next
From: Peter Geoghegan
Date:
Subject: Re: [BUG]"FailedAssertion" reported in lazy_scan_heap() when running logical replication