Date: Mon, 19 Jun 2017 18:19:16 -0400
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Mark Rofail <markm.rofail@gmail.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>,
	Robert Haas <robertmhaas@gmail.com>,
	"pgsql-hackers@postgresql.org" <pgsql-hackers@postgresql.org>,
	David Steele <david@pgmasters.net>,
	Stephen Frost <sfrost@snowman.net>
Subject: Re: GSoC 2017: Foreign Key Arrays
Message-ID: <20170619221916.idtty7tiihai65f7@alvherre.pgsql>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: 
 <CAJvoCutPeRsPm2whZ7OxuvZr7UkTJk0530ygFe5GaJwgewEkOg@mail.gmail.com>
User-Agent: NeoMutt/20170306-137-4415bd-dirty (1.8.0)
Precedence: bulk
Sender: pgsql-hackers-owner@postgresql.org

Mark Rofail wrote:
> Okay, so major breakthrough.
> 
> *Updates:*
> 
>    - The operator @>(anyarray, anyelement) is now functional
>       - The segmentation fault was due to applying PG_FREE_IF_COPY on a
>       datum when it should only be applied on TOASTed inputs
>       - The only problem now is if for example you apply the operator as
>       follows  '{AAAAAAAAAA646'}' @> 'AAAAAAAAAA646' it maps to @>(anyarray,
>       anyarray) since 'AAAAAAAAAA646' is interpreted as char[] instead of Text
>    - Added some regression tests (src/test/regress/sql/arrays.sql) and
>    their results(src/test/regress/expected/arrays.out)
>    - wokred on the new GIN strategy, I don't think it would vary much from
>    GinContainsStrategy.

OK, that's great.

> *What I plan to do:*
> 
>    - I need to start working on the Referential Integrity code but I don't
>    where to start

You need to study the old patch posted by Marco Nenciarini.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers