From: Tom Lane <tgl@sss.pgh.pa.us>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: eugeny@zhuzhnev.com, pgsql-bugs <pgsql-bugs@lists.postgresql.org>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Subject: Re: BUG #17866: behavior does not match documentation
Date: Mon, 10 Apr 2023 13:11:31 -0400
Message-ID: <4181771.1681146691@sss.pgh.pa.us> (raw)
In-Reply-To: <3605E583-D445-42E8-8AA6-A9E6136EA0E1@yesql.se>
References: <17866-18eb70095b1594e2@postgresql.org>
<1944674.1679596295@sss.pgh.pa.us>
<EE5080A8-E4B2-413F-A604-58B1BFAD8942@yesql.se>
<2053300.1679608490@sss.pgh.pa.us>
<3605E583-D445-42E8-8AA6-A9E6136EA0E1@yesql.se>
Daniel Gustafsson <daniel@yesql.se> writes:
> On 23 Mar 2023, at 22:54, Tom Lane <tgl@sss.pgh.pa.us> wrote:
>> It's more readable for sure, and it duplicates what you got in pre-v14
>> versions, at least textually. I'm not sure I'd propose back-patching
>> this, but it feels like a good idea for HEAD.
> Agreed, I don't think this is material for backpatching.
Since we didn't get anything done about that for v16, I concluded
that adjusting the docs is a better idea. If anyone takes this
idea up in v17 or beyond, they can always revert fbbd7edca at that
time.
regards, tom lane
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-bugs@postgresql.org
Cc: tgl@sss.pgh.pa.us, daniel@yesql.se, pgsql-bugs@lists.postgresql.org, peter.eisentraut@enterprisedb.com
Subject: Re: BUG #17866: behavior does not match documentation
In-Reply-To: <4181771.1681146691@sss.pgh.pa.us>
* 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