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

From: shihao zhong <zhong950419(at)gmail(dot)com>
To: Manav Kumar <mkumar(at)yugabyte(dot)com>
Cc: 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 03:46:53
Message-ID: CAGRkXqRN5EQTZp4XQQgJ7EL8B+ypkziMKi9Xm-v8rM-M9a0zeA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hi Manav,

I am not sure if this is a bug.

The long name still finds the right schema. Only the text you read
back is longer.

SET truncates because the parser truncates identifiers. If you give
SET a quoted string, it behaves just like set_config().

Thanks,
SHihao

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message shihao zhong 2026-11-04 05:42:55 Re: BUG #19780: gtsvector_picksplit() reads uninitialized data when called with three entries
Previous Message shihao zhong 2026-11-04 03:34:22 Re: BUG #19817: CREATE UNIQUE INDEX on a partitioned table can silently attach an invalid, not-ready child index, le