From: Tom Lane <tgl@sss.pgh.pa.us>
To: Wells Oliver <woliver@padres.com>
Cc: pgsql-admin@postgresql.org <pgsql-admin@postgresql.org>
Subject: Re: Unique operator error w/ concatenation
Date: Thu, 28 Jul 2011 16:37:10 -0400
Message-ID: <5004.1311885430@sss.pgh.pa.us> (raw)
In-Reply-To: <7E1773C5-185E-48FB-B6DC-FED4DD19D317@padres.com>
References: <7E1773C5-185E-48FB-B6DC-FED4DD19D317@padres.com>
Wells Oliver <woliver@padres.com> writes:
> Folks, experiencing an odd issue. The following on an 8.4 server: select 'foo'::text || 123
> Blows up, saying:
> ERROR: operator is not unique: text || integer
> LINE 1: select 'fo'::text || 123;
> ^
> HINT: Could not choose a best candidate operator. You might need to add explicit type casts.
> But on another postgres 8.4 server, it properly returns a concatenated string.
> Any tips on how/where I can track down why/where there might be duplicate operators?
psql's "\do ||" might help. Presumably somebody's stuck a user-defined
operator named || into that database ...
regards, tom lane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: tgl@sss.pgh.pa.us, woliver@padres.com
Subject: Re: Unique operator error w/ concatenation
In-Reply-To: <5004.1311885430@sss.pgh.pa.us>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox