From: | Dave Cramer <davecramer(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | 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 00:27:53 |
Message-ID: | CADK3HHLhbMZApqh-CEvd-igz9pKA7QmQU79FMKruegLCeNDCEA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Sat, 10 Apr 2021 at 20:24, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Dave Cramer <davecramer(at)gmail(dot)com> writes:
> > One of our tests purposely throws an error which returns
> > "ERROR: R interpreter parse error" on linux
> > and
> > "WARNING: R interpreter parse error" on windows.
>
> That's quite bizarre. What is the actual error level according to
> the source code, and where is the error being thrown exactly?
>
> I recall that elog.c has some code to force ERROR up to FATAL or
> PANIC in some cases, but it shouldn't ever promote a non-error to
> an ERROR.
>
Well it really is an ERROR, and is being downgraded on windows to WARNING.
I was hoping someone familiar with the code could remember something before
I dig into this tomorrow.
Thanks,
Dave
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2021-04-11 00:34:00 | Re: PL/R regression on windows, but not linux with master. |
Previous Message | Tom Lane | 2021-04-11 00:24:04 | Re: PL/R regression on windows, but not linux with master. |