On Dec 6, 2010, at 10:43 AM, Tom Lane wrote:
> That's an interesting idea, but I'm not sure it's wise to design around
> the assumption that we won't need substitutions ever. What I was
> thinking was that we should try to limit knowledge of the substitution
> behavior to the extension definition files and the implementation of
> CREATE EXTENSION itself. I don't agree with exposing that information
> at the SQL level.
>
> (On the other hand, if we *could* avoid using any explicit
> substitutions, it would certainly ease testing of extension files no?
> They'd be sourceable into psql then.)
Yes. And extension authors would not have to remember to include the magic line (which at any rate would break
extensionsfor earlier versions of PostgreSQL).
Best,
dAvid
