Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uHeTp-006jZW-Dl for pgsql-sql@arkaria.postgresql.org; Wed, 21 May 2025 08:07:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1uHeTo-004VVu-7L for pgsql-sql@arkaria.postgresql.org; Wed, 21 May 2025 08:07:12 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uHeTn-004VVj-Ti for pgsql-sql@lists.postgresql.org; Wed, 21 May 2025 08:07:11 +0000 Received: from mail-qv1-xf36.google.com ([2607:f8b0:4864:20::f36]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uHeTl-00061d-0O for pgsql-sql@lists.postgresql.org; Wed, 21 May 2025 08:07:11 +0000 Received: by mail-qv1-xf36.google.com with SMTP id 6a1803df08f44-6f8b10b807fso70152426d6.1 for ; Wed, 21 May 2025 01:07:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yugabyte.com; s=google; t=1747814827; x=1748419627; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=Be4jQFYWIi4UmsEH2n4J9dukNKBKwVc3TIG5vfXIgKk=; b=h08ROMqZOFtITldfMuYxAEou2hGEBKUKPTcGC/n+Pfa/aNYKnY/j6W2CDCDSGd2qDg 2TNJ+QK9lNu6pGI0HIlJaM4J7d1nHwYZv7MAHHKnP956QK3c2L9ODb7g4bhYqAUHeKj4 WbGX2xSQhonKHIjYUJGH54Kj6amtQCPiLnmsk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1747814827; x=1748419627; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=Be4jQFYWIi4UmsEH2n4J9dukNKBKwVc3TIG5vfXIgKk=; b=av6OB5MEWNM5a/nyycteBI/lIbB9sH0boPnS7hZ8TSNoIJgHEchLPabLfjERMg50eL tMSPCUjGlpaW1yEpsxEjp70VneZubw9qCbYTatiG6A8gBwq+aF5ricjWC7GlbznETkwY BmnyMSfIpux1iK+q+0UgmA3zuUnh7KAiy4mGFYWW/1BAa23q3huWSb16ApomKKJ8taWS gc6NXYaZLghWcbx4orU/EcPCRoaAX5+0nIUWPdG/KsRPZUZ4vpK4VHAUqfMXuJl6xo7u XoFtbkZdkHHpsUjDMTlPPZ6c1eKZmxYOi/G0VXo3hxa8SNuGpNnuA1uOfuAJVQDjcX8K T9HA== X-Gm-Message-State: AOJu0YyG7prM0XTS2Z3Dv/Ut8sqigzurr2nLUuMJc+E72ZMbUrxkpIu1 o81kqcqBcCNoDEV1TBapJVhdf4NRNz8NV7ogPgg/++rOgMaKbLNFKYuD0OcAEzkHndFHYEOsgox 3pGfgwN32y2ucsXVYCUfuoiNEwlyklJcgxDrcebcE0Wj8VFneznllAyA= X-Gm-Gg: ASbGnct3QgpCWqhEiCFEez3CFvTNnNnJdZ5mMQkjlwDOJXdzbFojExAmQ9Bzk1bVFth 1kLwe6Y41Je09PbhehiWXiOWSnt/GL0GRDYOFgCS3M5uQD0jXFWHZl3+/ce1Ngv/bAwFVNdLYFQ qdbTvbfNrXn1KfRv5B9Kz9kiRuwqw7H4jMVnRSwANHO3KSauOLMwcYVkEqYxiLxKQ2qg== X-Google-Smtp-Source: AGHT+IGTvFoJWdA/csU1pvWb5L2lpckT4h5rBCg5h+j2DddwfgVYI26xbdCMzt7vOB4hpY1XSK3MJqzoz4M/nsl1378= X-Received: by 2002:a05:6214:483:b0:6e6:61a5:aa57 with SMTP id 6a1803df08f44-6f8b087cdfdmr298228256d6.14.1747814827035; Wed, 21 May 2025 01:07:07 -0700 (PDT) MIME-Version: 1.0 From: Manav Kumar Date: Wed, 21 May 2025 13:36:56 +0530 X-Gm-Features: AX0GCFv835Uge3238wyboYUVBNd_8JWf2XtQrsrKNAcnPpgBzCrmUIhrIHKI0U4 Message-ID: Subject: Confirming precedence order of Default for GUCs To: pgsql-sql@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000e625220635a0d91d" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000e625220635a0d91d Content-Type: text/plain; charset="UTF-8" Hi Team, Can you please correct me regarding the precedence order of overriding the DEFAULT values for GUC's. Is it right to say, GUC passed in the start up packet will override the default value set by using ALTER DATABASE/ROLE. ? I've verified by running locally. But in the https://arc.net/l/quote/qnpjwhcw (DOCS) it says ALTER DATABASE/ROLE can override the cmd line options passed in startup packet. Also just below that paragraph for Interaction with Shell, it says about startup/cmd line options only overriding the default set via alter system or postgresql.conf Please correct me is it correct order of applying the defaults: 1. Using start up packet (i.e using env var or passing cmd line option) 2. Using alter database/role 3. Setting via postgresql.conf or using alter system Looking forward to hearing the response. Thanks Manav --000000000000e625220635a0d91d Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,=C2=A0
Can you please correct me regarding the precedence order of overriding th= e DEFAULT values for GUC's.

Is it right to say, GUC passed in the start u= p packet will override the default value set by using ALTER DATABASE/ROLE. = ?=C2=A0
I've verified by running loca= lly.=C2=A0
But in the=C2=A0https://arc.net/l/quote/qnpjwhcw (DO= CS) it says ALTER DATABASE/ROLE can override the cmd line options passed in= startup packet.=C2=A0
Also just below that paragraph = for Interaction with Shell, it says about startup/cmd line options only ove= rriding the default set via alter system or postgresql.conf

Please correct me is it correct order of a= pplying the defaults:

1. Usi= ng start up packet (i.e using env var or passing cmd line option)
2. Using alter database/role
3. Setting vi= a postgresql.conf or using alter system

Looking forward to hearing the response.=C2=A0
Thanks
Manav
--000000000000e625220635a0d91d--