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
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 pgsql-bugs@postgresql.org" and mention checkpass_in volatility in the subject." instead
