Re: [HACKERS] ltree::text not immutable?

From: Christoph Berg <cb(at)df7cb(dot)de>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org, Joe Van Dyk <joe(at)tanga(dot)com>, "pgsql-bugs(at)postgresql(dot)org" <pgsql-bugs(at)postgresql(dot)org>
Subject: Re: [HACKERS] ltree::text not immutable?
Date: 2014-11-17 16:38:38
Message-ID: 20141117163838.GA5248@msg.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs pgsql-hackers

Re: Tom Lane 2014-11-17 <6903(dot)1416241481(at)sss(dot)pgh(dot)pa(dot)us>
> Christoph Berg <cb(at)df7cb(dot)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(at)df7cb(dot)de | http://www.df7cb.de/

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Tom Lane 2014-11-17 17:21:39 Re: [BUGS] ltree::text not immutable?
Previous Message Tom Lane 2014-11-17 16:24:41 Re: [BUGS] ltree::text not immutable?

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-11-17 16:50:22 Re: 9.5: Better memory accounting, towards memory-bounded HashAgg
Previous Message Andres Freund 2014-11-17 16:34:46 Re: logical decoding - reading a user catalog table