On Fri, Aug 7, 2015 at 9:21 AM, Tom Lane <t...@sss.pgh.pa.us> wrote: > Andreas Seltenreich <seltenre...@gmx.de> writes: >> Tom Lane writes: >>> On 08/01/2015 05:59 PM, Tom Lane wrote: >>>> Well, I certainly think all of these represent bugs: >>>> 1 | ERROR: could not find pathkey item to sort > >>> Hmm ... I see no error with these queries as of today's HEAD or >>> back-branch tips. I surmise that this was triggered by one of the other >>> recently-fixed bugs, though the connection isn't obvious offhand. > >> I still see this error in master as of b8cbe43, but the queries are >> indeed a pita to reproduce. The one below is the only one so far that >> is robust against running ANALYZE on the regression db, and also >> reproduces when I run it as an EXTRA_TEST with make check. > > Got that one, thanks! But we've seen this error message before in all > sorts of weird situations, so I wouldn't assume that all the cases you've > come across had the same cause.
(resurrecting an old thread) This is still failing: =# select indexdef from pg_catalog.pg_indexes where indexdef is not NULL; ERROR: XX000: cache lookup failed for index 2619 LOCATION: pg_get_indexdef_worker, ruleutils.c:1054 Do we want to improve at least the error message? -- Michael -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
