| From: | Alexander Lakhin <exclusion(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PQconnectdb/PQerrorMessage changed behavior on master |
| Date: | 2021-06-28 04:00:00 |
| Message-ID: | bc6f8071-eb77-2766-34b7-5fd0124ee399@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
27.06.2021 23:07, Tom Lane wrote:
>> While trying to use sqlsmith with postgres compiled from the master
>> branch, I've found that the PQerrorMessage() function now returns
>> non-informational but not empty error message after the successful
>> PQconnectdb() call.
> Yeah, see thread here:
>
> https://www.postgresql.org/message-id/20210506162651.GJ27406%40telsasoft.com
>
> sqlsmith is definitely Doing It Wrong there, but there's a
> reasonable question whether such coding is common.
Thanks for info! I agree that sqlsmith's check is incorrect, nonetheless
I was embarrassed by the incomplete error message.
Best regards,
Alexander
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Amit Langote | 2021-06-28 04:20:33 | Re: Deadlock risk while inserting directly into partition? |
| Previous Message | Amit Langote | 2021-06-28 03:58:51 | Re: Deadlock risk while inserting directly into partition? |