Re: issue in pgfdw_report_error()?
| От | Bharath Rupireddy |
|---|---|
| Тема | Re: issue in pgfdw_report_error()? |
| Дата | |
| Msg-id | CALj2ACV6bxCjYHzZRw6=95KyGWFUkxrf-94HGbbEZdx8LgpkhA@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: issue in pgfdw_report_error()? (Fujii Masao <masao.fujii@oss.nttdata.com>) |
| Ответы |
Re: issue in pgfdw_report_error()?
|
| Список | pgsql-hackers |
On Mon, Nov 22, 2021 at 8:17 AM Fujii Masao <masao.fujii@oss.nttdata.com> wrote:
> > Well, in that case, why can't we get rid of "(message_primary != NULL"
> > and just have "message_primary[0] != '\0' ? errmsg_internal("%s",
> > message_primary) : errmsg("could not obtain message string for remote
> > error")" ?
>
> That's possible if we can confirm that PQerrorMessage() never returns
> NULL all the cases. I'm not sure how much it's worth doing that, though..
> It seems more robust to check also NULL there.
Okay.
> > BTW, we might have to fix it in dblink_res_error too?
>
> Yeah, that's good idea. I included that change in the patch. Attached.
Thanks. pgfdw_report_error_v2 patch looks good to me.
Regards,
Bharath Rupireddy.
В списке pgsql-hackers по дате отправления: