chkpass_in should not be volatile - Mailing list pgsql-hackers

From Thom Brown
Subject chkpass_in should not be volatile
Date
Msg-id CAA-aLv59cVjWUkGfWKCaU4ZM3NXVQsH=OffU4zMmod=Xr+dBMQ@mail.gmail.com
Whole thread Raw
Responses Re: chkpass_in should not be volatile  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
...or at least according to the warning message:

postgres=# CREATE EXTENSION chkpass ;
WARNING:  type input function chkpass_in should not be volatile

Thom

pgsql-hackers by date:

Previous
From: Korbin Hoffman
Date:
Subject: hstore: add hstore_length function
Next
From: Dmitry Igrishin
Date:
Subject: Re: PATCH: Batch/pipelining support for libpq