Thom Brown <t...@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 -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
