Re: BUG #17866: behavior does not match documentation

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: eugeny(at)zhuzhnev(dot)com, pgsql-bugs <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Peter Eisentraut <peter(dot)eisentraut(at)enterprisedb(dot)com>
Subject: Re: BUG #17866: behavior does not match documentation
Date: 2023-04-10 18:33:45
Message-ID: F55AB595-8B7A-411F-BC7E-F16806C41D85@yesql.se
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 10 Apr 2023, at 19:11, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Daniel Gustafsson <daniel(at)yesql(dot)se> writes:
>> On 23 Mar 2023, at 22:54, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)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.

The more I think about it the more I lean towards not changing anything
(besides the docs which you did). It's been in two releases already and hardly
any complaints, so it seems to be have been quite well accepted.

--
Daniel Gustafsson

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Роман Осипов 2023-04-10 18:42:28 Incorrect number of rows inserted into partitioned table
Previous Message Tom Lane 2023-04-10 17:11:31 Re: BUG #17866: behavior does not match documentation