On Thu, Jul 26, 2018 at 2:06 PM, Tom Lane <t...@sss.pgh.pa.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
