Re: Cache lookup errors with functions manipulation object addresses - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: Cache lookup errors with functions manipulation object addresses
Date
Msg-id 20180914150723.q5qknqkeamc4w43n@alvherre.pgsql
Whole thread Raw
In response to Re: Cache lookup errors with functions manipulation object addresses  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: Cache lookup errors with functions manipulation object addresses  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers
On 2018-Sep-14, Alvaro Herrera wrote:

> I haven't looked at 0003 yet.

It's strange that pg_identify_object returns empty type in only some
cases (as seen in the regression test output) ... and this one
definitely does not make sense:

+SELECT * FROM pg_identify_object('pg_class'::regclass, 'pg_class'::regclass, -8); -- no column for relation
+     type     |   schema   |   name   |      identity       
+--------------+------------+----------+---------------------
+ table column | pg_catalog | pg_class | pg_catalog.pg_class
+(1 row)

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: Cache lookup errors with functions manipulation object addresses
Next
From: Masahiko Sawada
Date:
Subject: Re: when set track_commit_timestamp on, database system abort startup