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

From Peter Eisentraut
Subject Re: [v9.2] DROP Reworks Part.1 - Consolidate routines to handle DropStmt
Date
Msg-id 1310464432.5488.5.camel@fsopti579.F-Secure.com
Whole thread Raw
In response to Re: [v9.2] DROP Reworks Part.1 - Consolidate routines to handle DropStmt  (Robert Haas <robertmhaas@gmail.com>)
List 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.




pgsql-hackers by date:

Previous
From: Peter Eisentraut
Date:
Subject: Re: dropping table in testcase alter_table.sql
Next
From: Alban Hertroys
Date:
Subject: Re: [GENERAL] Creating temp tables inside read only transactions