> > We could change pg_attribute to another name, and create a view called
> > pg_attribute that never returned isdropped columns to the client. That
> > would allow clients to work cleanly, and the server to work cleanly.
>
> Another case where having an informational schema would eliminate the
> whole argument -- as the clients wouldn't need to touch the system
> tables.
Since postgres has so many features that standard SQL doesn't have (eg.
custom operators), how are they going to be shown in the information schema?
Chris
