Re: recent ALTER whatever .. SET SCHEMA refactoring

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp>
Cc: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: recent ALTER whatever .. SET SCHEMA refactoring
Date: 2013-01-08 13:04:39
Message-ID: CA+Tgmoa0hVTu31nqU2s+Pz-6WtrGd2rZaGRgzFzk+vquDRpejg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, Jan 8, 2013 at 4:05 AM, Kohei KaiGai <kaigai(at)kaigai(dot)gr(dot)jp> wrote:
> Does it make sense an idea to invoke AlterFunctionNamespace_oid()
> or AlterCollationNamespace_oid() from AlterObjectNamespace_internal()
> for checks of namespace conflicts?
> It can handle special cases with keeping modularity between common
> and specific parts. Let's consider function pointer when we have mode
> than 5 object classes that needs special treatment.

Unless I'm gravely mistaken, we're only talking about a handful of
lines of code. We have lots of functions, in objectaddress.c for
example, whose behavior is conditional on the type of object that they
are operating on. And we just write out all the cases. I'm not
understanding why we need to take a substantially more complex
approach here.

--
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 2013-01-08 13:20:42 Re: Improve compression speeds in pg_lzcompress.c
Previous Message Hannu Krosing 2013-01-08 11:24:32 Re: Improve compression speeds in pg_lzcompress.c