Re: ALTER OBJECT any_name SET SCHEMA name

From: Alvaro Herrera <alvherre(at)commandprompt(dot)com>
To: Dimitri Fontaine <dimitri(at)2ndquadrant(dot)fr>
Cc: Heikki Linnakangas <heikki(dot)linnakangas(at)enterprisedb(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: ALTER OBJECT any_name SET SCHEMA name
Date: 2010-11-03 21:18:32
Message-ID: 1288818872-sup-282@alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Excerpts from Dimitri Fontaine's message of mié nov 03 13:10:12 -0300 2010:

> Then, I think the ALTER EXTENSION foo SET SCHEMA name still has a use
> case, so I've prepared a simple patch to show the API usage before we
> get to refactor it all following Tom's asking. So there's a initial
> patch to see that in action.

FWIW I think you should use getObjectDescription, as in the attached
patch. (Note the patch is incomplete and does not compile because only
one caller to CheckSetNamespace has been fixed).

--
Álvaro Herrera <alvherre(at)commandprompt(dot)com>
The PostgreSQL Company - Command Prompt, Inc.
PostgreSQL Replication, Consulting, Custom Development, 24x7 support

Attachment Content-Type Size
0001-Use-getObjectDescription.patch application/octet-stream 4.4 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Alexander Korotkov 2010-11-03 21:23:41 Fix for seg picksplit function
Previous Message David E. Wheeler 2010-11-03 21:15:21 Re: why does plperl cache functions using just a bool for is_trigger