On Aug 31, 2015, at 4:58 PM, Tom Lane <t...@sss.pgh.pa.us> wrote: > In any case, there is plenty of precedent for hard-coding knowledge about > specific version updates into pg_upgrade. The question here is whether > it's feasible to handle extensions that way. I think we could reasonably > expect to know about cases where a formerly separate extension got > integrated into core,
+1 > but are there other cases where pg_upgrade would > need to ignore an extension in the old database? Not that I can think of, unless it’s already present because it was in template1 or something. David
smime.p7s
Description: S/MIME cryptographic signature
