| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL 12, JIT defaults |
| Date: | 2018-10-08 17:42:44 |
| Message-ID: | CAFj8pRBpdwVt4t_pXAkd7aUVWKu7hxwySab21Py6rsLWHwgiWQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>
> >I am thinking so simple number should be good enough. We can require
> >equality - Just I need a signal so some is wrong - better than Postgres
> >crash.
>
> It'd cause constant conflicts and / or we would regularly forget updating
> it. It's not that trivial to determine what influences ABI compatibility.
>
This can be checked by regress tests? I don't know. Maybe I am not too
friendly, I am sorry. I spent 20 minutes by searching phantom, because JIT
was active, although I wanted.
So any help against this situation can be welcome.
Regards
Pavel
> Andres
> --
> Sent from my Android device with K-9 Mail. Please excuse my brevity.
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-10-08 18:01:27 | Removing variant expected-output files for float-output differences |
| Previous Message | Tom Lane | 2018-10-08 17:41:49 | Re: PostgreSQL 12, JIT defaults |