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 16:40:06 +0200
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Sun, May 31, 2026, at 10:05, Joel Jacobson wrote:
> 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:

v8 fixes another nondeterministic isolation-test ordering issue seen by
cfbot on the FreeBSD machine.

0001 and 0003 are unchanged from v7.

/Joel

Attachments:

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

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

  [application/x-gzip] v8-0003-Add-information_schema.view_constraint_usage.patch.gz (2.9K, ../[email protected]/4-v8-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