> A more serious objection is that this will break client applications
> that know about the pg_aggregate table. However, 7.3 is already going
> to force a lot of reprogramming of clients that inspect system tables,
> because of the addition of namespaces. Restructuring pg_aggregate
> doesn't seem like it makes life all that much worse.
How about putting a note in the 7.3 release that tells them not to rely on
sequential attnums in tn pg_attribute anymore. That should make it easier
to implement column dropping in the future?
Chris
