On 11/11/2015 11:31 AM, Tom Lane wrote: > After sleeping on it, the best compromise I can think of is to add an > "Assert(false)" after the WARNING report for the shared-catalogs case. > This will make the failure un-missable in any development build, while > not breaking production builds' ability to recover from corner cases > we might not've foreseen.
That sounds like a good answer to me. > Of course, if you run an assert-enabled build in production, you might > possibly lose. But that's never been recommended practice. Yeah, there are plenty of other ways you would lose on that proposition. Joe -- Crunchy Data - http://crunchydata.com PostgreSQL Support for Secure Enterprises Consulting, Training, & Open Source Development
signature.asc
Description: OpenPGP digital signature
