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

2010-07-03 Thread Robert Haas
On Sat, Jul 3, 2010 at 11:47 AM, Tom Lane wrote: > Robert Haas writes: >> 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 lif

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

2010-07-03 Thread Tom Lane
Robert Haas writes: > 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 >

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

2010-07-03 Thread Robert Haas
On Thu, Jul 1, 2010 at 11:19 AM, Asko Tiidumaa 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

[HACKERS] reassign owned to change the ownership for op class and family

2010-07-01 Thread Asko Tiidumaa
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);