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

From Justin Pryzby
Subject cache lookup failed for statistics object 123
Date
Msg-id 20210505210947.GA27406@telsasoft.com
Whole thread Raw
Responses Re: cache lookup failed for statistics object 123
List pgsql-hackers
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().

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.

-- 
Justin

Attachment

pgsql-hackers by date:

Previous
From: Andrew Dunstan
Date:
Subject: Re: Bogus collation version recording in recordMultipleDependencies
Next
From: Thomas Munro
Date:
Subject: Re: Bogus collation version recording in recordMultipleDependencies