Re: [BUGS] ltree::text not immutable? - Mailing list pgsql-hackers

From Christoph Berg
Subject Re: [BUGS] ltree::text not immutable?
Date
Msg-id 20141117163838.GA5248@msg.df7cb.de
Whole thread Raw
In response to Re: [BUGS] ltree::text not immutable?  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: [BUGS] ltree::text not immutable?  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
Re: Tom Lane 2014-11-17 <6903.1416241481@sss.pgh.pa.us>
> Christoph Berg <cb@df7cb.de> writes:
> > In HEAD, there's this WARNING now:
> > WARNING:  type input function chkpass_in should not be volatile
> 
> Yeah, that's intentional.
> 
> > IMHO built-in functions (even if only in contrib) shouldn't be raising
> > warnings - the user can't do anything about the warnings anyway, so
> > they shouldn't get notified in the first place.
> 
> The point is to find out how many people care ...

Is the point of this to figure out whether to fix this properly, or to
revert to the old code? The current status isn't something that should
be released with 9.5.

> > (Catched by Debian's postgresql-common testsuite)
> 
> ... and by "people", I do not mean test suites.

Well atm this breaks the building of 9.5 packages. This means we are
not going to find out if anyone cares by this way :)

Christoph
-- 
cb@df7cb.de | http://www.df7cb.de/



pgsql-hackers by date:

Previous
From: Steve Singer
Date:
Subject: Re: logical decoding - reading a user catalog table
Next
From: Andres Freund
Date:
Subject: Re: logical decoding - reading a user catalog table