Re: reassign owned to change the ownership for op class and family

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: reassign owned to change the ownership for op class and family
Дата
Msg-id AANLkTimQAEAwtl_8ziFIv_wVycYEWe8s9IwN8UJD6Er_@mail.gmail.com
обсуждение исходный текст
Ответ на reassign owned to change the ownership for op class and family  (Asko Tiidumaa <asko.tiidumaa@gmail.com>)
Ответы Re: reassign owned to change the ownership for op class and family  (Tom Lane <tgl@sss.pgh.pa.us>)
Список pgsql-hackers
On Thu, Jul 1, 2010 at 11:19 AM, Asko Tiidumaa <asko.tiidumaa@gmail.com> wrote:
> Currently REASSIGN OWNED complains "unexpected classid" for operator
> class and family.
>
> For example,
>
> create two users, user1 and user2
>
> under user1:
> create type oxetype as enum ('oxe1');
> create operator class oxeops
> default for type oxetype using btree as
> function 1 array_lower(anyarray,integer);
>
> and then observe "unexpected classid" error:
> reassign owned by user1 to user2
>
> So I propose a patch that goes against head, and it would be great to
> get it backported to at least 8.3 branch
>
> Comments?

Committed, with minor adjustments.  This is actually against 8.3; it
needs to use the new syscache macros in head (which I did).

http://archives.postgresql.org/pgsql-committers/2010-02/msg00174.php

I wonder if we should think about back-patching just the syscache.h
portion of that patch.  It would simplify back-patching, and might
make life easier for people trying to write extensions that are
compatible with multiple PG versions, too.

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


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Heikki Linnakangas
Дата:
Сообщение: Re: Keepalive for max_standby_delay
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: nvarchar notation accepted?