Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bUzwS-0002na-Ja for pgsql-admin@arkaria.postgresql.org; Wed, 03 Aug 2016 17:26:52 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bUzwS-00071Y-6J for pgsql-admin@arkaria.postgresql.org; Wed, 03 Aug 2016 17:26:52 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUzul-0004Us-3V for pgsql-admin@postgresql.org; Wed, 03 Aug 2016 17:25:07 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bUzuh-00088s-M2 for pgsql-admin@postgresql.org; Wed, 03 Aug 2016 17:25:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id u73HP1fq032216; Wed, 3 Aug 2016 13:25:01 -0400 From: Tom Lane To: John Scalia cc: "pgsql-admin@postgresql.org" Subject: Re: Proper syntax to update an hstore key-value pair In-reply-to: References: <22859.1470234864@sss.pgh.pa.us> <28358.1470242851@sss.pgh.pa.us> Comments: In-reply-to John Scalia message dated "Wed, 03 Aug 2016 12:12:48 -0500" Date: Wed, 03 Aug 2016 13:25:01 -0400 Message-ID: <32215.1470245101@sss.pgh.pa.us> X-Pg-Spam-Score: -3.1 (---) List-Archive: List-Help: List-ID: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: X-Mailing-List: pgsql-admin Precedence: bulk Sender: pgsql-admin-owner@postgresql.org John Scalia 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 -- Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin