Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>, PgHacker <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Refactoring on DROP/ALTER SET SCHEMA/ALTER RENAME TO statement
Date: 2011-11-30 20:33:14
Message-ID: CA+TgmobPvN3tfwGf4a=hxd8-nz2nqRKbGf5WXX4HOYzDGpKYKw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sun, Nov 27, 2011 at 3:14 PM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2011-11-30 20:37:24 Re: loss of transactions in streaming replication
Previous Message Robert Haas 2011-11-30 20:30:08 Re: Inverse convertion for pg_mb2wchar