Re: Set readonly transaction per transaction

Dave Cramer <pg@fastcrypt.com> wrote:
> On 8 December 2014 at 03:17, Alexandor84 <oleksandr.sukhotskyi@gmail.com> wrote:

>> No one faced with such problem?

> Apparently not. I doubt many people use pgbouncer in transaction
> mode.
>
> Can you explain why you are using transaction mode ?

Hey, now!  I often recommend transaction mode, because I have seen
applications scale to a much higher concurrency that way.  See:

https://wiki.postgresql.org/wiki/Number_Of_Database_Connections

and:

http://stackoverflow.com/questions/10419665/how-does-pgbouncer-help-to-speed-up-django/10420469#10420469

As a suggestion to the original poster, how about executing:

SET read_only = on;

... as the first statement of a new transaction?

--
Kevin Grittner
EDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company