| 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 17:25:01 |
| Message-ID: | 32215.1470245101@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:
> 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 | John Scalia | 2016-08-03 19:29:57 | Re: Proper syntax to update an hstore key-value pair |
| Previous Message | John Scalia | 2016-08-03 17:12:48 | Re: Proper syntax to update an hstore key-value pair |