Личный кабинет
Укажите e-mail, на который будет выслан код восстановления пароля.
На указанный вами адрес e-mail был выслан код подтверждения аккаунта. Введите полученный код для продолжения:
Введите новый пароль два раза:
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 volatileSee 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?
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 volatileSee 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.
В списке pgsql-hackers по дате отправления: