From: | Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> |
---|---|
To: | Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: issue in pgfdw_report_error()? |
Date: | 2021-11-22 02:47:03 |
Message-ID: | 192a2107-7e37-64d6-c5b3-c45448ba2e9e@oss.nttdata.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 2021/11/20 1:16, Bharath Rupireddy wrote:
> With the existing code, it emits "" for message_primary[0] == '\0'
> cases but with the patch it emits "could not obtain message string for
> remote error".
Yes.
> 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.
> 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.
Regards,
--
Fujii Masao
Advanced Computing Technology Center
Research and Development Headquarters
NTT DATA CORPORATION
Attachment | Content-Type | Size |
---|---|---|
pgfdw_report_error_v2.patch | text/plain | 1.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Fujii Masao | 2021-11-22 02:55:25 | Re: Shouldn't postgres_fdw report warning when it gives up getting result from foreign server? |
Previous Message | Peter Geoghegan | 2021-11-22 02:13:51 | Removing more vacuumlazy.c special cases, relfrozenxid optimizations |