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

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>, PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [v9.2] DROP Reworks Part.1 - Consolidate routines to handle DropStmt
Date: 2011-07-12 09:53:52
Message-ID: 1310464432.5488.5.camel@fsopti579.F-Secure.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
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.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Alban Hertroys 2011-07-12 10:08:18 Re: [HACKERS] Creating temp tables inside read only transactions
Previous Message Peter Eisentraut 2011-07-12 09:46:09 Re: dropping table in testcase alter_table.sql