Re: [PATCH] Introduce unified support for composite GUC options

From: Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>
To: Чумак Антон <a(dot)chumak(at)postgrespro(dot)ru>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: [PATCH] Introduce unified support for composite GUC options
Date: 2025-09-22 07:01:46
Message-ID: CAFj8pRCcUHQt5UAjM9eSdst196U1c+HFr4T326AVuErxYxJGMw@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Hi

what is use case for this?

Regards

Pavel

po 22. 9. 2025 v 8:55 odesílatel Чумак Антон <a(dot)chumak(at)postgrespro(dot)ru>
napsal:

> Hello hackers,
>
> The new version of the patch adds support for multi-line writing of
> composite type values in the postgresql.conf file. Hidden fields have also
> been added. Such fields may be required to protect the private part of the
> state of a composite option from an external user. In order for the field
> to be hidden, the composite type signature must describe only the field
> type without the field name.
>
> Please note that all allocated resources used within hidden fields should
> use only guc_malloc. This is necessary to automatically release resources.
>
> The patch applies cleanly to the master
> (9fc7f6ab7226d7c9dbe4ff333130c82f92749f69)
>
> Best regards,
> Anton Chumak
>
>

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Fujii Masao 2025-09-22 07:19:14 Re: Documentation fix on pgbench \aset command
Previous Message Чумак Антон 2025-09-22 06:55:22 Re: [PATCH] Introduce unified support for composite GUC options