"Jim C. Nasby" <decibel@decibel.org> writes:
> Start with a clean plate. Yes, we'll end up with an ugly schema name,
> but after the exiting pg_catalog is removed in a few versions, we can go
> back to pg_catalog.
Huh? pg_catalog isn't going away, and none of this discussion has
anything to do with changing the system catalogs themselves. In any
case, creating these views with the idea that we will change their
locations later is a nonstarter. People are going to be putting
the fully qualified paths into their applications.
> The idea of using a GUC to control which version of the schema you get
> is also very interesting, though I don't know how workable it is.
It could be spelled "schema_path" ... otherwise I don't see any way to
do it. But I'm not sure it helps any to make two separate schemas.
Most admin-type apps wouldn't want to depend on the value of schema_path
(psql sure wouldn't, for instance) so they'd still have to change if
only to nail down the schema they want in each query.
regards, tom lane
