From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
---|---|
To: | Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | alter operator class |
Date: | 2007-03-19 17:43:23 |
Message-ID: | 45FECBBB.7010804@sigaev.ru |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
'alter operator class' command isn't "dumpable":
postgres=# ALTER OPERATOR CLASS name_pattern_ops USING btree RENAME TO namep_ops;
postgres=# create table n (a name);
postgres=# create index ni on n (a namep_ops);
% pg_dump postgres | psql wow
....
ERROR: operator class "namep_ops" does not exist for access method "btree"
That's because command doesn't track such changes in pg_depend or somewhere
else. For now that kind of changes doesn't make a significant sense - nobody
will change names/properties of system objects, but I'm afraid that will be
often for fulltext configurations. How can we avoid such situations?
Forbid changes on built-in objects?
'alter operator class .. owner to ...' doesn't dump too.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
From | Date | Subject | |
---|---|---|---|
Next Message | Florian G. Pflug | 2007-03-19 17:53:32 | Re: modifying the tbale function |
Previous Message | Bruce Momjian | 2007-03-19 17:32:24 | Re: who gets paid for this |