Re: Broken handling of NULLs in TG_ARGV - Mailing list pgsql-hackers

From Jim Nasby
Subject Re: Broken handling of NULLs in TG_ARGV
Date
Msg-id 5543EFDE.5060000@BlueTreble.com
Whole thread Raw
In response to Re: Broken handling of NULLs in TG_ARGV  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
On 4/30/15 6:44 PM, Tom Lane wrote:
> There isn't any such thing as a genuine SQL NULL argument; the examples
> you provided are just text strings, not SQL NULLs.  In order to make them
> be actual nulls, we would have to redefine the arguments as being
> expressions of some sort, which is problematic for backwards-compatibility
> reasons.  It also seems like rather a lot of new mechanism to add for
> something with (evidently) near-zero user demand.

Ahh, I thought the array started life as an actual array, not char **. 
So yeah, not nearly as easy to fix. :(
-- 
Jim Nasby, Data Architect, Blue Treble Consulting
Data in Trouble? Get it in Treble! http://BlueTreble.com



pgsql-hackers by date:

Previous
From: Peter Geoghegan
Date:
Subject: Re: INSERT ... ON CONFLICT UPDATE/IGNORE 4.0
Next
From: Robert Haas
Date:
Subject: Re: CTE optimization fence on the todo list?