Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET

From: Daniel Gustafsson <daniel(at)yesql(dot)se>
To: shihao zhong <zhong950419(at)gmail(dot)com>
Cc: Manav Kumar <mkumar(at)yugabyte(dot)com>, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET
Date: 2026-11-04 15:27:17
Message-ID: D8FF6928-6867-4ECC-AD5C-E893487CF9C1@yesql.se
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

> On 4 Nov 2026, at 15:47, shihao zhong <zhong950419(at)gmail(dot)com> wrote:

> The attached 001 adds ParameterStatus to VALID_LONG_MESSAGE_TYPE

I haven't had time to investigate what could be done here (if anything), but
I'm sure it isn't weakening protections to handle a synthetic case.

--
Daniel Gustafsson

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Ayush Tiwari 2026-11-04 15:48:57 Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
Previous Message shihao zhong 2026-11-04 14:47:20 Re: set_config(‘search_path’) does not truncate names over 63 bytes, unlike SET