| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Joe Conway <mail(at)joeconway(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>, Dave Cramer <davecramer(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: PL/R regression on windows, but not linux with master. |
| Date: | 2021-04-11 16:42:58 |
| Message-ID: | 2688684.1618159378@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
I wrote:
> Joe Conway <mail(at)joeconway(dot)com> writes:
>> Would an equivalent "PGWARNING" be something we are open to adding and
>> back-patching?
> It's not real obvious how pl/r could solve this in a reliable way
> otherwise, so adding that would be OK with me, but I wonder whether
> back-patching is going to help you any. You'd still need to compile
> against older headers I should think. So I'd suggest
> (1) add PGWARNING in HEAD only
Concretely, maybe like the attached?
regards, tom lane
| Attachment | Content-Type | Size |
|---|---|---|
| make-PGWARNING-PGERROR-universally-available.patch | text/x-diff | 1.4 KB |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2021-04-11 16:43:15 | Re: PANIC: wrong buffer passed to visibilitymap_clear |
| Previous Message | Tom Lane | 2021-04-11 16:16:04 | Re: psql - add SHOW_ALL_RESULTS option |