Re: read only transactions

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Jon Nelson" <jnelson+pgsql(at)jamponi(dot)net>, <pgsql-performance(at)postgresql(dot)org>
Subject: Re: read only transactions
Date: 2010-10-12 18:58:13
Message-ID: 4CB4697502000025000368A4@gw.wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> wrote:

> Are there any performance implications (benefits) to executing
> queries in a transaction where
> SET TRANSACTION READ ONLY;
> has been executed?

I don't think it allows much optimization in any current release.

It wouldn't be a bad idea to use it where appropriate, though, as
future releases might do something with it. If you include this on
the BEGIN statement, that will save a round trip.

-Kevin

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Tom Lane 2010-10-12 19:33:44 Re: read only transactions
Previous Message Jesper Krogh 2010-10-12 18:22:01 Re: Slow count(*) again...