On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane <[email protected]> wrote: > Thom Brown <[email protected]> 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. >
Thom, how did you end up encountering this? While it seems to have resulted in the right effect (here) maybe we could have written: "WARNING: If you are reading this please email [email protected]" and mention checkpass_in volatility in the subject." instead David J.
