| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | John Scalia <jayknowsunix(at)gmail(dot)com> |
| 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:49:35 |
| Message-ID: | 16363.1470253775@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
John Scalia <jayknowsunix(at)gmail(dot)com> writes:
> 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.
Hmm. AFAICS, every extant version of hstore ought to provide
operator ||(hstore,hstore)
and no other operator named ||. You might try comparing the results
of "\dx+ hstore" across your installations.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | John Scalia | 2016-08-03 20:19:40 | Re: Proper syntax to update an hstore key-value pair |
| Previous Message | John Scalia | 2016-08-03 19:29:57 | Re: Proper syntax to update an hstore key-value pair |