Albe
Cc: Edson Richter ;
pgsql-performance@lists.postgresql.org
Subject: [EXT] Re: Read-only connectios optimizatios
External Email: Use caution with links and attachments.
You can still block vacuum from running if you have long running (or very
aggressive) read transactions. I don’t think
You can still block vacuum from running if you have long running (or very
aggressive) read transactions. I don’t think they are very helpful or
performant from a Postgres engine perspective.
They can be helpful in application development because they will fail if devs
attempt any mutations insid
On Sat, 2025-01-25 at 14:55 +, Edson Richter wrote:
> -Connections are established using the jdbc "readonly" attribute.
>
> Does PostgreSQL perform any optimization on queries in this scenario to avoid
> establishing locks? Or are these queries treated like any other?
The only difference that
Scenario:
-PostgreSQL 13 latest version;
-I have some reporting users, with "SELECT,REFERENCES" permissions on all
tables in the public schema.
-Connections are established using the jdbc "readonly" attribute.
Does PostgreSQL perform any optimization on queries in this scenario to avoid
establis
