Postgres Pro
Downloads
Home   >   mailing lists

Re: [HACKERS] GSoC 2017: Foreign Key Arrays - Mailing list pgsql-hackers

From Mark Rofail
Subject Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Date
Msg-id CAJvoCutsqAGau6q+L_JRrTZozmwts8DYrO_oGJaJmrWjBd3rgA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] GSoC 2017: Foreign Key Arrays  ("Joel Jacobson" <joel@compiler.org>)
Responses Re: [HACKERS] GSoC 2017: Foreign Key Arrays  ("Joel Jacobson" <joel@compiler.org>)
List pgsql-hackers
Tree view
Hey Joel,

test opr_sanity                   ... FAILED

                    AND binary_coercible(p2.opcintype, p1.amoplefttype));
  amopfamily | amopstrategy | amopopr
------------+--------------+---------
-(0 rows)
+       2745 |            5 |    6105
+(1 row)

-- Operators that are primary members of opclasses must be immutable (else
-- it suggests that the index ordering isn't fixed).  Operators that are
This is due using anycompatiblearray for the left operand in @>>. 
To solve this problem we need to use @>>(anyarray,anyelement) or introduce a new opclass for gin indices. 
These are the two approaches that come to mind to solve this. Which one is the right way or is there another solution I am not aware of?
That’s why I’m asking this on the mailing list, to get the community’s input.

/Mark

pgsql-hackers by date:

Previous
From: Mark Rofail
Date:
Subject: Re: [HACKERS] GSoC 2017: Foreign Key Arrays
Next
From: Amit Kapila
Date:
Subject: Re: logical replication seems broken