From: | John Scalia <jayknowsunix(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "pgsql-admin(at)postgresql(dot)org" <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Proper syntax to update an hstore key-value pair |
Date: | 2016-08-03 19:29:57 |
Message-ID: | CABzCKRCJr3FbajAafcjw=XibOFZ6PAw57YfcenC+9ypYpLezxQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Well, I discovered that I had different versions of hstore across several
databases. Some were 1.1 and others were 1.3. On the 1.3 hstore versions,
the \do *.|| produces a public hstore - hstore operator, while the 1.1
shows the same as public.hstore. Maybe I just wasn't casting this far
enough. On both versions that operator shows as being in the public schema.
My search path does include that.
On Wed, Aug 3, 2016 at 12:25 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> John Scalia <jayknowsunix(at)gmail(dot)com> writes:
> > Your instruction to run "\do ||" did return a list including left arg
> type
> > as text and right arg type as text. The list does report the schema as
> > pg_catalog as opposed to the schema I'm actually working in at the
> moment,
>
> Yeah, that's the built-in "text || text" operator. The question is where
> is the "hstore || hstore" operator added by the hstore extension. If
> you're not seeing that in \do output, then it's not in your search path.
>
> Actually, it might be better to try "\do *.||", which should show all
> operators named || regardless of which schema they are in and whether
> that schema is in your path.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2016-08-03 19:49:35 | Re: Proper syntax to update an hstore key-value pair |
Previous Message | Tom Lane | 2016-08-03 17:25:01 | Re: Proper syntax to update an hstore key-value pair |