From: | Чумак Антон <a(dot)chumak(at)postgrespro(dot)ru> |
---|---|
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 06:55:22 |
Message-ID: | f176e-68d0f300-1-263b70c@46704559 |
Views: | Whole Thread | Raw Message | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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
Attachment | Content-Type | Size |
---|---|---|
v2-0002-added-guc-options-for-test-purposes.patch | text/x-patch | 23.1 KB |
v2-0001-Composite-data-types-have-been-added-to-the-GUC.patch | text/x-patch | 147.3 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Pavel Stehule | 2025-09-22 07:01:46 | Re: [PATCH] Introduce unified support for composite GUC options |
Previous Message | shveta malik | 2025-09-22 06:33:19 | Re: Logical Replication of sequences |