Re: BUG #17866: behavior does not match documentation

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Daniel Gustafsson <daniel(at)yesql(dot)se>
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 17:11:31
Message-ID: 4181771.1681146691@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Daniel Gustafsson 2023-04-10 18:33:45 Re: BUG #17866: behavior does not match documentation
Previous Message Tom Lane 2023-04-10 13:46:59 Re: ERROR: no NOT NULL constraint found to drop