The following bug has been logged on the website:
Bug reference: 7758
Logged by: Daniel Migowski
Email address: dmigow...@ikoffice.de
PostgreSQL version: 9.1.7
Operating system: Windows, bug Linux seems also affected
Description:
Hi,
here is a small example of operat
The following bug has been logged on the website:
Bug reference: 7760
Logged by: Alan Cummings
Email address: acummi...@aperiogroup.com
PostgreSQL version: 9.1.7
Operating system: Ubuntu Linux 10.04.1
Description:
We found 6 duplicated primary keys in a table. All fie
dmigow...@ikoffice.de writes:
> When inserted into an empty DB on an 9.1.2 system, then pg_dump will
> generate wrong CUMMUTATOR clauses, but only for the first operator:
> ...
> Sadly, when I use these operators in my real world database running on
> 9.1.7, the problem is still there:
Indeed, I d
I found an example that breaks on Postgres 9.1.7! Just define TWO operators!
Try this:
-- Start of SQL script ---
begin;
CREATE OR REPLACE FUNCTION text_natsort_gt(text, text) RETURNS boolean AS
'SELECT bttext_pattern_cmp($1,$2) > 0'
LANGUAGE 'sql' IMMUTABLE STRICT COST 1;
C
Daniel Migowski writes:
> DROP OPERATOR IF EXISTS #<#(text,text) CASCADE;
> CREATE OPERATOR #<#(
> PROCEDURE = text_natsort_lt,
> LEFTARG = text,
> RIGHTARG = text,
> COMMUTATOR = #>#,
> RESTRICT = scalarltsel,
> JOIN = scalarltjoinsel);
> DROP OPERATOR IF EXISTS #>#(text,text) CAS
I wrote:
> I believe we've looked at this in the past, and not found any cure
> that wasn't worse than the disease.
BTW, the previous discussion that I was vaguely remembering is here:
http://archives.postgresql.org/pgsql-hackers/2010-09/msg02035.php
regards, tom lane
--
