Re: BUG #17077: about three parameters in postgresql 13.3

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>
Cc: Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com>, "leiyanliang(at)highgo(dot)com" <leiyanliang(at)highgo(dot)com>, "pgsql-bugs(at)lists(dot)postgresql(dot)org" <pgsql-bugs(at)lists(dot)postgresql(dot)org>
Subject: Re: BUG #17077: about three parameters in postgresql 13.3
Date: 2021-07-17 19:21:39
Message-ID: 79947.1626549699@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:
> Maybe include "SET NAMES" while at it? It drove me crazy when I found
> out that was accepted, last year.

That is documented, but only on the SET page, because there isn't a GUC
by that name.

regards, tom lane

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Noah Misch 2021-07-17 20:12:40 Re: CREATE INDEX CONCURRENTLY does not index prepared xact's data
Previous Message Alvaro Herrera 2021-07-17 17:24:08 Re: BUG #17077: about three parameters in postgresql 13.3