Re: [HACKERS] chkpass_in should not be volatile

2016-06-03 Thread David G. Johnston
On Fri, Jun 3, 2016 at 10:41 AM, Thom Brown wrote: > On 3 June 2016 at 15:26, David G. Johnston > wrote: > >> On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane wrote: >> >>> Thom Brown writes: >>> > ...or at least according to the warning message: >>> > postgres=# CREATE EXTENSION chkpass ; >>> > WARNI

Re: [HACKERS] chkpass_in should not be volatile

2016-06-03 Thread Thom Brown
On 3 June 2016 at 15:26, David G. Johnston wrote: > On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane wrote: > >> Thom Brown writes: >> > ...or at least according to the warning message: >> > postgres=# CREATE EXTENSION chkpass ; >> > WARNING: type input function chkpass_in should not be volatile >> >>

Re: [HACKERS] chkpass_in should not be volatile

2016-06-03 Thread David G. Johnston
On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane wrote: > Thom Brown writes: > > ...or at least according to the warning message: > > postgres=# CREATE EXTENSION chkpass ; > > WARNING: type input function chkpass_in should not be volatile > > See thread here: > > > https://www.postgresql.org/message-id

Re: [HACKERS] chkpass_in should not be volatile

2016-06-03 Thread Tom Lane
Thom Brown writes: > ...or at least according to the warning message: > postgres=# CREATE EXTENSION chkpass ; > WARNING: type input function chkpass_in should not be volatile See thread here: https://www.postgresql.org/message-id/flat/CACfv%2BpL2oX08SSZSoaHpyC%3DUbfTFmPt4UmVEKJTH7y%3D2QMRCBw%40