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 1uSaim-009uRs-Vs for pgsql-jdbc@arkaria.postgresql.org; Fri, 20 Jun 2025 12:19:53 +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 1uSail-001Ajf-1x for pgsql-jdbc@arkaria.postgresql.org; Fri, 20 Jun 2025 12:19:51 +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 1uSaik-001AjX-PU for pgsql-jdbc@lists.postgresql.org; Fri, 20 Jun 2025 12:19:51 +0000 Received: from mail-qv1-xf2d.google.com ([2607:f8b0:4864:20::f2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.96) (envelope-from ) id 1uSaij-0037Yd-0Y for pgsql-jdbc@lists.postgresql.org; Fri, 20 Jun 2025 12:19:51 +0000 Received: by mail-qv1-xf2d.google.com with SMTP id 6a1803df08f44-6fb01566184so14342296d6.1 for ; Fri, 20 Jun 2025 05:19:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yugabyte.com; s=google; t=1750421987; x=1751026787; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=E2byleX5RyX3Bm6GavYlIwF6LKQHxj66asI4BhpLiEk=; b=ioAg01aQu6t/201dUBycaZaHNiVAArBvTKwSoPdufKpefBPNaXC4ZEfh40aRMhDdZ7 bBShiQmY0p5M0bXKDCBQRAqee9hsvyHczlTaNz220Jcmo3t6yyVQUEMNoZttXv4Q+W7b a4xIOYZP6ydWYelDn+C4fn9LuA/KIhPwbVdYY= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1750421987; x=1751026787; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=E2byleX5RyX3Bm6GavYlIwF6LKQHxj66asI4BhpLiEk=; b=q27/jBlI7O5/DMJ4Jan6dzLZcwOrI4J3rCra2VE3DRu96itXXEM5uSFBTKUELjMaq8 jkOHKzZJvdqDz9kpBATP8xYb0EQmOP1o03ObMl2sny1OGsP3HCpi+DgesWEwdg5oOPxA IcVL+7lOiINQvU7ikoVr1ziCreNlaaTLs36XmFAriGO/1xzh4OJarWgtwWtURHqAFEvH GbLNxMhovXFPHCyMD4Jkt8n8yS6aMXMKqwrdM/tisnSzwIx9ZxPBo7iAovbsr1tNy7y1 UNzMqIdcyXrp8TSiwfq4pH7oADNS8e3aA8nKdVnu02aBh4oxXIQ3IBer3cSm/wxoGnQK 8/YA== X-Gm-Message-State: AOJu0YyiwSzYJ38jvYIYBSBr7syOyIbT+rCSBUZy+/0wTKeyVSo4jQgK CwODlvevhRqfSh5cg9CQxy0n0S4/JahqsH9hpPK5XUWNqVLpvrnps0Fif4A5by4SqLemv9ap6/9 injNakxxBvLkikYG0U7q3bIa1HFNPSzq6XBXXiZDK/HYBghfqmB4Nb50= X-Gm-Gg: ASbGncsGg6282nYIR/E/nI4pSRJiG0Gy/HxX0igQDYUpyIM3Q5fdVqUjl55LO/y39TB RV4FH+RgzFonURB7zF+n6VtXWRCXKzvNt5ct4Z1WAbbLVBbV5NPnfm2gDOEmvayfwHYi4ufVVmM EXqewPqnmk9vej4zKL6MsmdY28l6qVbUO8TiVDWgwsVUCbWLwQzzgqW0cZXPLNALAnaVzrMl2Rc SSYBw== X-Google-Smtp-Source: AGHT+IEDHvCZ0VD3Xgf/6OSdglQxn5vRf6Bg4bkG3aWwFvdMwb8qSfeuijp9oGIwhLjc9jO/9+nYno9Fa/GG//yZEzY= X-Received: by 2002:ad4:5e8b:0:b0:6fa:baa2:b59e with SMTP id 6a1803df08f44-6fd0a57abe3mr44241556d6.37.1750421986883; Fri, 20 Jun 2025 05:19:46 -0700 (PDT) MIME-Version: 1.0 From: Manav Kumar Date: Fri, 20 Jun 2025 17:49:34 +0530 X-Gm-Features: Ac12FXy0gu9fuHn6i7ycteut_o8he8-0pSK1o7FTdMDdibcCkfB30XuvvVaBKWw Message-ID: Subject: Unable to set guc via setProperty To: pgsql-jdbc@lists.postgresql.org Content-Type: multipart/alternative; boundary="000000000000bc4eaa0637ffe023" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bc4eaa0637ffe023 Content-Type: text/plain; charset="UTF-8" Hi Team, I've a doubt regarding passing guc variables in start up packet as key value pairs instead of in options. I'm unable to set jdbc:postgresql://10.150.3.175:6433/postgres?&geqo=off m geqo to 'off'. I don't want to use "options" rather pass directly key value pairs similar to what JDBC driver internally does. Neither setProperty("geqo", "off") works in this case. Can someone let me know why I can't do it? I learnt or from code, it's seen the key value pairs has higher precedence or override the guc values passed via cmdline option("options") field when both passed in start up packet. That's why with JDBC, even i try to set "options - DateStyle to 'Postgres,DM'Y'" we are unable to change value as DateStyle is also passed as key value by driver with 'ISO' which has higher precedence. Thanks Manav --000000000000bc4eaa0637ffe023 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team,
I've a doubt regarding passing guc variab= les=C2=A0in start up packet as key value pairs instead of in options.=C2=A0=

I'm unable=C2=A0to set=C2=A0jdbc:po= stgresql://10= .150.3.175:6433/postgres?&geqo=3Doff
m geqo to &#= 39;off'. I don't want to use "options" rather pass direct= ly key value pairs similar to what JDBC driver internally does.=C2=A0
=

Neither=C2=A0setProperty("geqo", "off&qu= ot;) works in this case.
Can someone let me know why I can't = do it?=C2=A0

I learnt or from code, it's seen = the key value pairs has higher=C2=A0precedence or override the guc values p= assed via cmdline option("options") field when both passed in sta= rt up packet.=C2=A0
That's why with JDBC, even i try to set &= quot;options - DateStyle to 'Postgres,DM'Y'" we are unable= to change value as DateStyle is also passed as key value by driver with &#= 39;ISO' which has higher precedence.=C2=A0=C2=A0
Thanks
=
Manav
--000000000000bc4eaa0637ffe023--