Re: Unable to set guc via setProperty - Mailing list pgsql-jdbc

From David G. Johnston
Subject Re: Unable to set guc via setProperty
Date
Msg-id CAKFQuwaLd4tOYxE-Hw8CCWw2KZN_GooAmg6uHcOFF+et6hDNxw@mail.gmail.com
Whole thread Raw
Responses Re: Unable to set guc via setProperty
List pgsql-jdbc
On Friday, June 20, 2025, Manav Kumar <mkumar@yugabyte.com> wrote:
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? 

Probably because that isn’t how things work…connection properties are set using set property and gucs aren’t connection properties - though there is a pass-through connection property called options that can hold a list of gucs to set.
 

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.  


IIUC the driver must control date style to operate correctly.  And as a user you shouldn’t care because you’ll be using Java classes to process dates.

David J.

pgsql-jdbc by date:

Previous
From: Laurenz Albe
Date:
Subject: Re: Understanding DateStyle guc in startup packet
Next
From: Dave Cramer
Date:
Subject: Re: Unable to set guc via setProperty