Re: Does creating readOnly connections, when possible, free up resources in Postgres?

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "David Kremer" <jkorders(at)gmx(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: Does creating readOnly connections, when possible, free up resources in Postgres?
Date: 2019-01-27 19:31:41
Message-ID: 16252.1548617501@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

"David Kremer" <jkorders(at)gmx(dot)com> writes:
> I saw that when you create a JDBC connection, you can specify readOnly=true. Would doing so somehow help Postgres manage its other connections? Perhaps Postgres, knowing that a connection is readOnly and will never even attempt to do an update, will free up some internal resources for other connections. Is this accurate?

No.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Adrian Klaver 2019-01-27 19:55:36 Re: Query help
Previous Message David Kremer 2019-01-27 18:11:09 Does creating readOnly connections, when possible, free up resources in Postgres?