Re: [PATCH v4] Add \warn to psql - Mailing list pgsql-hackers

From Tom Lane
Subject Re: [PATCH v4] Add \warn to psql
Date
Msg-id 19572.1562642940@sss.pgh.pa.us
Whole thread Raw
In response to Re: [PATCH v4] Add \warn to psql  (Bruce Momjian <bruce@momjian.us>)
Responses Re: [PATCH v4] Add \warn to psql  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
Bruce Momjian <bruce@momjian.us> writes:
> On Fri, Jul  5, 2019 at 11:29:03PM +0200, David Fetter wrote:
>>> I fixed that, but I'm wondering if we should back-patch that fix
>>> or leave the back branches alone.

>> +0.5 for back-patching.

> Uh, if this was done in a major release I am thinking we have to mention
> this as an incompatibility, which means we should probably not backpatch
> it.

How is "clearly doesn't match the documentation" not a bug?

            regards, tom lane



pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11
Next
From: Ibrar Ahmed
Date:
Subject: Re: pgbench - add \aset to store results of a combined query