Peter Eisentraut <pe...@eisentraut.org> writes:
> -       strlcpy(errbuf, strerror(ERR_GET_REASON(ecode)), SSL_ERR_LEN);
> +       strerror_r(ERR_GET_REASON(ecode), errbuf, SSL_ERR_LEN);

Most of libpq gets at strerror_r via SOCK_STRERROR for Windows
portability.  Is that relevant here?

                        regards, tom lane


Reply via email to