Личный кабинет
Укажите e-mail, на который будет выслан код восстановления пароля.
На указанный вами адрес e-mail был выслан код подтверждения аккаунта. Введите полученный код для продолжения:
Введите новый пароль два раза:
YES!\dx yields intarray was installed (back in the 9.1 days, maybe) and that was clobbering the @> operator.Looking into the implications of removing intarray now that we're at 9.6, seems harmless, but will do my due diligence.Thanks Jeff.On Sun, Aug 20, 2017 at 3:15 PM, Jeff Janes <jeff.janes@gmail.com> wrote:On Sun, Aug 20, 2017 at 1:28 PM, Wells Oliver <wells.oliver@gmail.com> wrote:Why is this happening and what can I do to get my GIN indexes working? Thanks!What extensions do you have installed in each database? I bet one of them (like intarray) redefines @> for one of your databases. Try fully qualifying the operator. OPERATOR(pg_catalog.@>)Cheers,Jeff-- Wells Oliverwells.oliver@gmail.com
On Sun, Aug 20, 2017 at 1:28 PM, Wells Oliver <wells.oliver@gmail.com> wrote:Why is this happening and what can I do to get my GIN indexes working? Thanks!What extensions do you have installed in each database? I bet one of them (like intarray) redefines @> for one of your databases. Try fully qualifying the operator. OPERATOR(pg_catalog.@>)Cheers,Jeff
Why is this happening and what can I do to get my GIN indexes working? Thanks!
В списке pgsql-general по дате отправления: