| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | David Fetter <david(at)fetter(dot)org>, Arthur Zakirov <a(dot)zakirov(at)postgrespro(dot)ru>, Fabien COELHO <coelho(at)cri(dot)ensmp(dot)fr>, Corey Huinker <corey(dot)huinker(at)gmail(dot)com>, PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [PATCH v4] Add \warn to psql |
| Date: | 2019-07-09 03:29:00 |
| Message-ID: | 19572.1562642940@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ibrar Ahmed | 2019-07-09 03:29:31 | Re: pgbench - add \aset to store results of a combined query |
| Previous Message | Michael Paquier | 2019-07-09 03:26:33 | Re: PGOPTIONS="-fh" make check gets stuck since Postgres 11 |