Re: chkpass_in should not be volatile

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Thom Brown <thom(at)linux(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: chkpass_in should not be volatile
Date: 2016-06-03 13:56:31
Message-ID: 11985.1464962191@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

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.

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-06-03 14:02:55 Re: Reviewing freeze map code
Previous Message Michael Paquier 2016-06-03 13:44:38 Re: Problem with dumping bloom extension