Re: chkpass_in should not be volatile

Поиск
Список
Период
Сортировка
От Thom Brown
Тема Re: chkpass_in should not be volatile
Дата
Msg-id CAA-aLv75MiNgS-1c0L_NQfBMMigcrubDWbETOXnV2xZm6K1WjA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: chkpass_in should not be volatile  ("David G. Johnston" <david.g.johnston@gmail.com>)
Ответы Re: chkpass_in should not be volatile
Список pgsql-hackers
Дерево обсуждения
On 3 June 2016 at 15:26, David G. Johnston <david.g.johnston@gmail.com> wrote:
On Fri, Jun 3, 2016 at 9:56 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
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

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.

Thom

В списке pgsql-hackers по дате отправления: