| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Vik Fearing <vik(dot)fearing(at)2ndquadrant(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: 11beta crash/assert caused by parameter type changes |
| Date: | 2018-07-26 19:14:53 |
| Message-ID: | CA+TgmoYt5Nvg_b1mKs+D6AaSN2WxDpXQJ9Dgcmu88zc6Ya1-MA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Jul 26, 2018 at 2:06 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I was about to add Andrew's example as a test case (also shown in
> attached), but realized that there's a problem: just as noted in
> the similar test for named-composite-type changes a bit above there,
> the failure fails to fail in CLOBBER_CACHE_ALWAYS builds.
Sorry if this is a dumb question, but why does that happen? I thought
that the idea was that CLOBBER_CACHE_ALWAYS shouldn't change
semantics.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2018-07-26 19:20:08 | Re: 11beta crash/assert caused by parameter type changes |
| Previous Message | Vik Fearing | 2018-07-26 18:40:14 | Re: Enhancement request: enable FIRST/LAST_value() also as a regular aggregate (not only as windowing function) |