[HACKERS] Re: [COMMITTERS] pgsql: Remove objname/objargs split for referringto objects - Mailing list pgsql-hackers

From Alvaro Herrera
Subject [HACKERS] Re: [COMMITTERS] pgsql: Remove objname/objargs split for referringto objects
Date
Msg-id 20170316155624.cjaweygkplodj66i@alvherre.pgsql
Whole thread Raw
In response to Re: [HACKERS] [COMMITTERS] pgsql: Remove objname/objargs split for referring to objects  (Michael Paquier <michael.paquier@gmail.com>)
Responses [HACKERS] Re: [COMMITTERS] pgsql: Remove objname/objargs split for referring toobjects  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Michael Paquier wrote:

> What are you using as CFLAGS? As both typenames should be normally
> set, what about initializing those fields with NULL and add an
> assertion like the attached?

Actually, my compiler was right -- this was an ancient bug I introduced
in 9.5 (commit a61fd533), and this new warning was my compiler being a
bit smarter now for some reason.  The problem is we were trying to
extract String value from a TypeName node, which obviously doesn't work
very well.

I pushed a real fix, not just a compiler-silencer, along with a few
lines in object_address.sql to make sure it works properly.  Maybe we
need a few more tests cases for other parts of pg_get_object_address.

Pushed fix, backpatched to 9.5.

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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZEto max_wal_send
Next
From: David Steele
Date:
Subject: [HACKERS] Re: [PATCH] guc-ify the formerly hard-coded MAX_SEND_SIZE tomax_wal_send