Re: [v9.2] DROP Reworks Part.1 - Consolidate routines to handle DropStmt

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>
To: Robert Haas <robertmhaas@gmail.com>
Cc: Kohei KaiGai <kaigai@kaigai.gr.jp>, PgHacker <pgsql-hackers@postgresql.org>
Date: 2011-07-12T09:53:52Z
Lists: pgsql-hackers
On ons, 2011-07-06 at 12:40 -0400, Robert Haas wrote:
> I think perhaps we should create a
> big static array, each row of which would contain:
> 
> - ObjectType
> - system cache ID for OID lookups
> - system catalog table OID for scans
> - attribute number for the name attribute, where applicable (see
> AlterObjectNamespace)
> - attribute number for the namespace attribute
> - attribute number for the owner attribute
> - ...and maybe some other properties 

Yeah, I was thinking of the same thing a while ago.

For large parts of the DDL support for collations I literally copied
over the conversion support and ran sed over it.  That must be made
better.  Take that as a test case if you will.