public inbox for [email protected]  

help / color / mirror / Atom feed

From: Joel Jacobson <[email protected]>
To: Laurenz Albe <[email protected]>
To: pgsql-hackers <[email protected]>
Cc: Arne Roland <[email protected]>
Cc: Anders Granlund <[email protected]>
Cc: Andreas Karlsson <[email protected]>
Cc: Vik Fearing <[email protected]>
Subject: Re: Key joins
Date: Sun, 31 May 2026 10:05:28 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Fri, May 29, 2026, at 18:20, Laurenz Albe wrote:
> On Fri, 2026-05-29 at 15:21 +0200, Joel Jacobson wrote:
>> We actually originally considered TO and FROM as keywords for indicating
>> direction, but FROM in a join clause causes confusion with the FROM
>> clause itself.  Our user discussions over the last three years indicates
>> that arrows are clearer and less ambiguous.
>> 
>> It's also worth to mention that SQL/PGQ also uses ASCII arrows to
>> indicate direction for its graph pattern syntax.
>
> I understand the problem with FROM, and I have no objection to the
> arrows.

Thanks for reviewing.

v7 updates 0002 to match the revised Change Proposal wording for
GROUPING SETS/ROLLUP/CUBE:

* Row-coverage facts can now pass through GROUPING SETS, ROLLUP, and
  CUBE when one expanded grouping set contains all key columns under the
  same key identity.  This is less conservative than v6: subtotal rows
  with NULLs in omitted grouping columns do not invalidate row coverage,
  since row coverage is about containment of all-non-null key values.

* Uniqueness and not-null handling for grouping sets remain conservative.
  GROUPING SETS/ROLLUP/CUBE do not by themselves prove referenced
  uniqueness or not-nullness; a following DISTINCT or simple GROUP BY can
  still provide uniqueness where needed.

* 0001 and 0003 are unchanged from v6.

/Joel

Attachments:

  [application/x-gzip] v7-0001-Serialize-routine-definition-changes-with-depende.patch.gz (1.9K, ../[email protected]/2-v7-0001-Serialize-routine-definition-changes-with-depende.patch.gz)
  download

  [application/x-gzip] v7-0002-Implement-FOR-KEY-join-support.patch.gz (178.1K, ../[email protected]/3-v7-0002-Implement-FOR-KEY-join-support.patch.gz)
  download

  [application/x-gzip] v7-0003-Add-information_schema.view_constraint_usage.patch.gz (2.9K, ../[email protected]/4-v7-0003-Add-information_schema.view_constraint_usage.patch.gz)
  download

view thread (26+ messages)  latest in thread

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: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Key joins
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox