From: Tom Lane <tgl@sss.pgh.pa.us>
To: John Scalia <jayknowsunix@gmail.com>
cc: "pgsql-admin@postgresql.org" <pgsql-admin@postgresql.org>
Subject: Re: Proper syntax to update an hstore key-value pair
In-reply-to: 
 <CABzCKRBdeQ-D5KQnHtu5tjMBNfhr4NMr-f3ZUQs6fpcsiGLhAA@mail.gmail.com>
References: 
 <CABzCKRBa6859u6NEcmyddc0iknoMbmMao4AAVpTUS4i464J0uA@mail.gmail.com>
 <22859.1470234864@sss.pgh.pa.us>
 <CABzCKRBdeQ-D5KQnHtu5tjMBNfhr4NMr-f3ZUQs6fpcsiGLhAA@mail.gmail.com>
Comments: In-reply-to John Scalia <jayknowsunix@gmail.com>
	message dated "Wed, 03 Aug 2016 10:19:29 -0500"
Date: Wed, 03 Aug 2016 12:47:31 -0400
Message-ID: <28358.1470242851@sss.pgh.pa.us>
Precedence: bulk
Sender: pgsql-admin-owner@postgresql.org

John Scalia <jayknowsunix@gmail.com> writes:
> You are correct, though, Tom, that the hstore extension is 1.1. Is there
> some other, not =>,  construct I should be using?

The hstore(text,text) function replaces that.

> Curiously, I just checked
> my personal sandbox database (9.5) and the hstore there is 1.3, but like I
> said earlier the update succeeds on that one.

That's pretty hard to believe, because 9.5 disallows => as an operator
name altogether.

I still suspect that you have got a search path problem.  You might
try, eg, "\do ||" in psql and see whether hstore || is listed or not.
Also check which schema \dx says the hstore extension is in in each
database.

			regards, tom lane


-- 
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin