Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bV2fY-0002Qj-2E for pgsql-admin@arkaria.postgresql.org; Wed, 03 Aug 2016 20:21:36 +0000 Received: from localhost ([127.0.0.1] helo=postgresql.org) by malur.postgresql.org with smtp (Exim 4.84_2) (envelope-from ) id 1bV2fX-0006sa-1T for pgsql-admin@arkaria.postgresql.org; Wed, 03 Aug 2016 20:21:35 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1bV2do-0004tG-4t for pgsql-admin@postgresql.org; Wed, 03 Aug 2016 20:19:48 +0000 Received: from mail-oi0-x241.google.com ([2607:f8b0:4003:c06::241]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.84_2) (envelope-from ) id 1bV2dl-00019Q-K5 for pgsql-admin@postgresql.org; Wed, 03 Aug 2016 20:19:46 +0000 Received: by mail-oi0-x241.google.com with SMTP id d204so20966181oig.3 for ; Wed, 03 Aug 2016 13:19:45 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=content-transfer-encoding:from:mime-version:subject:date:message-id :references:cc:in-reply-to:to; bh=7E22ymkd3qMVzSUrYO8Olyn+618M6wu2eS5WQ6+1MO8=; b=dtXHMiY+y2G+/6ehDWYhFTc4TZwT4tr48nXzKPM5c1I2VJ8DrLooWzMafzYd9hFjUs CyiR5isW5e58k73Y27lZqfP6dbqze9jWsXMMiqGp2njbgflSpyQWzsPj3qWU2XeZ69Z8 EiyduE7wN6MxTTpGcX+FFcmZHIsL2RikyrNIuIO2rr08mxr3tcKi4enOXVcGwAZcsHGZ iqs++qUpJoYo4PEdFMNBEWSOqqCllzksY+DfLCHfOCQQ0ifmHJT5mdMnFwfVV56V1sLo pBqctVUNFKibzRCIETPwcLeNQPXq2AbAFt9Z1KZm/11G2eZJYKX6GAHQqm8QeM+GqtXx PR0Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-transfer-encoding:from:mime-version :subject:date:message-id:references:cc:in-reply-to:to; bh=7E22ymkd3qMVzSUrYO8Olyn+618M6wu2eS5WQ6+1MO8=; b=i9jZ+rzisrfBEucRQxE82PO6r+T0yuluTYn9Vofjv4yiYOEvf7y+YDNdLCG/AKOjc2 Z95d/zdzCGCE1Z/fAydj6/wA7qQQ21FOjwe5TfD/iLodXjYYm4T0a6mDF1q/zmPHdrHN AUV62roCHuKf/hcW76xPgEHVdU9aWZTSQTF5POpofToY2hij+fXHU8Sk5IcV05lSxLn2 ZWeyJD+JrHWlYsfyTtNmuBoSTSZcJRzRgrA2YyPu5JpQESTJonUtDUXqMCrhw6qYlXLA 4ZGMmJZ0XsO5e6i1RLh5I21ZhtEPGGTuej7ibwJ80G5Xqm2CQ7gS+acrpi8ysLqiGxrX D/Mw== X-Gm-Message-State: AEkoouv10j0s6LrysWtzWBO9tnU4j7ZPRjfu4u9DoORPktDM7+go5eRSXYeLpr3EbM2XYg== X-Received: by 10.157.44.74 with SMTP id f68mr31488824otb.80.1470255584894; Wed, 03 Aug 2016 13:19:44 -0700 (PDT) Received: from ?IPv6:2605:6000:f686:8500:417:6250:da03:97ea? ([2605:6000:f686:8500:417:6250:da03:97ea]) by smtp.gmail.com with ESMTPSA id j2sm4552490oih.19.2016.08.03.13.19.43 (version=TLS1 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 03 Aug 2016 13:19:44 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable From: John Scalia Mime-Version: 1.0 (1.0) Subject: Re: Proper syntax to update an hstore key-value pair Date: Wed, 3 Aug 2016 15:19:40 -0500 Message-Id: References: <22859.1470234864@sss.pgh.pa.us> <28358.1470242851@sss.pgh.pa.us> <32215.1470245101@sss.pgh.pa.us> <16363.1470253775@sss.pgh.pa.us> Cc: "pgsql-admin@postgresql.org" In-Reply-To: <16363.1470253775@sss.pgh.pa.us> To: Tom Lane X-Mailer: iPad Mail (13G34) X-Pg-Spam-Score: -2.7 (--) 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 Sorry if I wasn't clear. Every version I found did include that operator, b= ut there were differences in how they were defined. In the 1.1 version the = arguments for "||" were listed as being public.hstore while in 1.3 the args= were just hstore. I'm going to revisit my tests tomorrow morning. I've got= ten all my versions now at 1.3, but it's been a very long day since I start= ed at 6:30 am this morning. Thanks for your help, everyone. Sent from my iPad > On Aug 3, 2016, at 2:49 PM, Tom Lane wrote: >=20 > John Scalia 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 sche= ma. >> My search path does include that. >=20 > Hmm. AFAICS, every extant version of hstore ought to provide >=20 > operator ||(hstore,hstore) >=20 > and no other operator named ||. You might try comparing the results > of "\dx+ hstore" across your installations. >=20 > regards, tom lane --=20 Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin