From: David Steele <david@pgmasters.net>
To: Peter Eisentraut <peter.eisentraut@2ndquadrant.com>
To: Georgios Kokolatos <gkokolatos@protonmail.com>
To: pgsql-hackers@lists.postgresql.org
Subject: Re: Allow an alias to be attached directly to a JOIN ... USING
Date: Fri, 5 Mar 2021 12:00:20 -0500
Message-ID: <19cab8ea-7106-2017-e018-d65feffb90ad@pgmasters.net> (raw)
In-Reply-To: <4c4727e2-2797-7f02-3529-f504e843d2ea@2ndquadrant.com>
References: <454638cf-d563-ab76-a585-2564428062af@2ndquadrant.com>
<88018eae-d949-be66-7fec-924213213b49@technowledgy.de>
<160502135578.7362.9015197269135176959.pgcf@coridan.postgresql.org>
<4c4727e2-2797-7f02-3529-f504e843d2ea@2ndquadrant.com>
On 11/14/20 3:49 AM, Peter Eisentraut wrote:
> On 2020-11-10 16:15, Georgios Kokolatos wrote:
>> I noticed that this patch fails on the cfbot.
>> For this, I changed the status to: 'Waiting on Author'.
>>
>> Cheers,
>> //Georgios
>>
>> The new status of this patch is: Waiting on Author
>
> Here is a rebased and lightly retouched patch.
There don't seem to be any objections to just documenting the slight
divergence from the spec.
So, does it make sense to just document that and proceed?
Regards,
--
-David
david@pgmasters.net
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: david@pgmasters.net, peter.eisentraut@2ndquadrant.com, gkokolatos@protonmail.com, pgsql-hackers@lists.postgresql.org
Subject: Re: Allow an alias to be attached directly to a JOIN ... USING
In-Reply-To: <19cab8ea-7106-2017-e018-d65feffb90ad@pgmasters.net>
* 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