Re: [HACKERS] strange relcache.c debug message - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [HACKERS] strange relcache.c debug message
Date
Msg-id 5296.1509545747@sss.pgh.pa.us
Whole thread Raw
List pgsql-hackers
Alvaro Herrera <alvherre@2ndquadrant.com> writes:
> While messing with BRIN bugs, I noticed this debug message in the server
> log:
> 2017-11-01 12:33:24.042 CET [361429] DEBUG:  rehashing catalog cache id 14 for pg_opclass; 17 tups, 8 buckets en
carácter194 
> notice that at the end it says "at character 194".  I suppose that's
> because of some leftover errposition() value, but why is it being
> reported in this message?

IIRC, there are places in the parser that set up an error callback that
will attach an errposition to any message at all that gets reported within
a particular chunk of code.  It's meant to catch something like "name not
found" but could produce this too.
        regards, tom lane


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

pgsql-hackers by date:

Previous
From: Craig Ringer
Date:
Subject: Re: [HACKERS] proposal: extend shm_mq to support more use cases
Next
From: Peter Eisentraut
Date:
Subject: Re: [HACKERS] pg_basebackup fails on Windows when using tablespacemapping