Re: chkpass_in should not be volatile

On Fri, Jun 3, 2016 at 10:41 AM, Thom Brown <thom(at)linux(dot)com> wrote:

> On 3 June 2016 at 15:26, David G. Johnston <david(dot)g(dot)johnston(at)gmail(dot)com>
> wrote:
>
>> On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>>
>>> Thom Brown <thom(at)linux(dot)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.
>>>
>>
>> Thom, how did you end up encountering this?
>>
>
> I built the extension and tried to create it. Not really anything other
> than that.
>
>
​I guess, "what was the motivation for creating the extension" would have
been a better question. Just a test suite for completeness or something
application-level?

David J.