Re: GiST support for inet datatypes
| От | Tom Lane |
|---|---|
| Тема | Re: GiST support for inet datatypes |
| Дата | |
| Msg-id | 1397.1393520181@sss.pgh.pa.us обсуждение |
| Ответ на | Re: GiST support for inet datatypes (Florian Pflug <fgp@phlo.org>) |
| Ответы |
Re: GiST support for inet datatypes
|
| Список | pgsql-hackers |
Florian Pflug <fgp@phlo.org> writes:
> Maybe I'm missing something, but isn't the gist of the problem here that
> pg_dump won't explicitly state the operator class if it's the default?
That's not a bug, it's a feature, for much the same reasons that pg_dump
tries to minimize explicit schema-qualification.
At least, it's a feature for ordinary dumps. I'm not sure whether it
might be a good idea for binary_upgrade dumps. That would depend on
our policy about whether a new opclass has to have a new (and necessarily
weird) name. If we try to make the new opclass still have the nicest
name then it won't help at all for pg_dump to dump the old name.
regards, tom lane
В списке pgsql-hackers по дате отправления: