pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Mark Rofail <markm.rofail@gmail.com>
Cc: Alexander Korotkov <aekorotkov@gmail.com>
Cc: Robert Haas <robertmhaas@gmail.com>
Cc: pgsql-hackers@postgresql.org <pgsql-hackers@postgresql.org>
Cc: David Steele <david@pgmasters.net>
Cc: Stephen Frost <sfrost@snowman.net>
Subject: Re: GSoC 2017: Foreign Key Arrays
Date: Mon, 19 Jun 2017 18:19:16 -0400
Message-ID: <20170619221916.idtty7tiihai65f7@alvherre.pgsql> (raw)
In-Reply-To: <CAJvoCutPeRsPm2whZ7OxuvZr7UkTJk0530ygFe5GaJwgewEkOg@mail.gmail.com>
List-Unsubscribe: <mailto:majordomo@postgresql.org?body=unsub%20pgsql-hackers>

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



view thread (200+ messages)  latest in thread

Message-ID: <20170619221916.idtty7tiihai65f7@alvherre.pgsql>
Permalink:  ../20170619221916.idtty7tiihai65f7@alvherre.pgsql/
Also on:    postgresql.org/message-id/20170619221916.idtty7tiihai65f7@alvherre.pgsql

 · 

reply

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-hackers@postgresql.org
  Cc: alvherre@2ndquadrant.com, markm.rofail@gmail.com, aekorotkov@gmail.com, robertmhaas@gmail.com, david@pgmasters.net, sfrost@snowman.net
  Subject: Re: GSoC 2017: Foreign Key Arrays
  In-Reply-To: <20170619221916.idtty7tiihai65f7@alvherre.pgsql>

* 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