Re: get/setReadOnly broken if default_transaction_read_only on

From: "Johann 'Myrkraverk' Oskarsson" <johann(at)2ndquadrant(dot)com>
To: PostgreSQL JDBC <pgsql-jdbc(at)postgresql(dot)org>
Subject: Re: get/setReadOnly broken if default_transaction_read_only on
Date: 2012-06-08 08:19:25
Message-ID: p32k49.x5p32k49.boku.md0y.gnus@asuka.myrkraverk.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-jdbc

Craig Ringer <ringerc(at)ringerc(dot)id(dot)au> writes:

> The JDBC driver really needs a way to grab everything it needs to know
> efficiently during initial connection setup, with some extensibility
> so connection parameters can specify other things to request and cache
> when the connection is first established.

Something like

SELECT current_setting( 'shared_buffers' )
UNION
SELECT current_setting( 'data_directory' );

for some randomly chosen settings? Of course the query will need to be
structured with key/values to be useful.

--
Johann Oskarsson http://www.2ndquadrant.com/ |[]
PostgreSQL Development, 24x7 Support, Training and Services --+--
|
Blog: http://my.opera.com/myrkraverk/blog/

In response to

Responses

Browse pgsql-jdbc by date

  From Date Subject
Next Message Віталій Тимчишин 2012-06-08 08:49:50 Re: get/setReadOnly broken if default_transaction_read_only on
Previous Message J Chapman Flack 2012-06-07 14:07:14 Re: get/setReadOnly broken if default_transaction_read_only on