Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>, takaram71(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #17767: psql: tab-completion causes warnings when standard_conforming_strings = off
Date: 2023-02-06 15:19:43
Message-ID: 2663396.1675696783@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> writes:
> Hmm, really? We could just remove it for 16; people will still be able
> to use the warnings mode in 15 for several years, so if they want to
> upgrade to 16+ they will have plenty of time to update their apps.

I think removing standard_conforming_strings = off might be a
bridge too far, even yet. Or were you speaking of removing
escape_string_warning? I could get behind that perhaps.
Making it default to off could be an even easier sell.

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alvaro Herrera 2023-02-06 15:22:09 Re: WAL segments removed from primary despite the fact that logical replication slot needs it.
Previous Message PG Bug reporting form 2023-02-06 14:48:44 BUG #17777: An assert failed in nodeWindowAgg.c