Re: chkpass_in should not be volatile - Mailing list pgsql-hackers

From Tom Lane
Subject Re: chkpass_in should not be volatile
Date
Msg-id 11985.1464962191@sss.pgh.pa.us
Whole thread Raw
In response to chkpass_in should not be volatile  (Thom Brown <thom@linux.com>)
Responses Re: chkpass_in should not be volatile  ("David G. Johnston" <david.g.johnston@gmail.com>)
List pgsql-hackers
Thom Brown <thom@linux.com> 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%40mail.gmail.com

Given the lack of complaints so far, maybe we could think about redefining
the behavior of chkpass_in.  I'm not very sure to what, though.
        regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: Problem with dumping bloom extension
Next
From: Robert Haas
Date:
Subject: Re: Reviewing freeze map code