Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
Date
Msg-id CA+TgmobPvN3tfwGf4a=hxd8-nz2nqRKbGf5WXX4HOYzDGpKYKw@mail.gmail.com
Whole thread Raw
In response to Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement  (Kohei KaiGai <kaigai@kaigai.gr.jp>)
Responses Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
List pgsql-hackers
On Sun, Nov 27, 2011 at 3:14 PM, Kohei KaiGai <kaigai@kaigai.gr.jp> wrote:
> If we add new properties that required by AlterObjectNamespace, as
> you suggested, it will allow to reduce number of caller of this routine
> mechanically with small changes.
> Should I try this reworking with this way?

Yeah, let's try that for starters, and then see if anything further
suggests itself.

> At least, AlterObjectNamespace already consolidate the point to check
> permissions.

Right.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: loss of transactions in streaming replication
Next
From: Robert Haas
Date:
Subject: Re: WIP: cross column stats revisited ...