Re: Fixing GIN for empty/null/full-scan cases
| От | Tom Lane |
|---|---|
| Тема | Re: Fixing GIN for empty/null/full-scan cases |
| Дата | |
| Msg-id | 29367.1294878920@sss.pgh.pa.us обсуждение |
| Ответ на | Re: Fixing GIN for empty/null/full-scan cases ("David E. Wheeler" <david@kineticode.com>) |
| Ответы |
Re: Fixing GIN for empty/null/full-scan cases
|
| Список | pgsql-hackers |
"David E. Wheeler" <david@kineticode.com> writes:
> Thanks, working on it now. I'm restoring a dump from 8.4, but got these erors:
> pg_restore: [archiver (db)] Error from TOC entry 3227; 2616 46485 OPERATOR CLASS gin__int_ops postgres
> pg_restore: [archiver (db)] could not execute query: ERROR: function ginarrayextract(anyarray, internal) does not
exist
> Did a signature change or something?
Yeah. I think if you just load up the current contrib/intarray first,
you'll be fine (ignore all the object-already-exists errors).
> Is there something that needs a compatibility interface of some kind?
No, what we need is a decent extension package manager ;-)
regards, tom lane
В списке pgsql-hackers по дате отправления: