Re: For SELECT statement (just a reading one, no 'FOR UPDATE'), isCOMMIT or ROLLBACK preferred? - Mailing list pgsql-general

From Rob Sargent
Subject Re: For SELECT statement (just a reading one, no 'FOR UPDATE'), isCOMMIT or ROLLBACK preferred?
Date
Msg-id 3C2ED636-A81D-4BC4-92A1-38634F5DD5D2@gmail.com
Whole thread Raw
In response to For SELECT statement (just a reading one, no 'FOR UPDATE'), is COMMITor ROLLBACK preferred?  (David Wall <d.wall@computer.org>)
Responses Re: For SELECT statement (just a reading one, no 'FOR UPDATE'), isCOMMIT or ROLLBACK preferred?  (David Wall <d.wall@computer.org>)
List pgsql-general

> On Aug 25, 2019, at 1:09 PM, David Wall <d.wall@computer.org> wrote:
>
> Using the latest PostgreSQL, does it matter if my code does a ROLLBACK or a COMMIT on an non-modifying SELECT
statement? My impression is they'd be the same as nothing is changed and therefore there's nothing to commit or
rollback,but wondered if there was any difference in how they are processed by Postgres? 
>
> Thanks,
> David
>
>
>
In interactive psql, both issue a warning that there is no current transaction.  What is your auto-commit setting and
howis your code sent to the server? 


pgsql-general by date:

Previous
From: "Johann 'Myrkraverk' Oskarsson"
Date:
Subject: Re: pgcharts on Ubuntu 18.04 ?
Next
From: Howard Wells
Date:
Subject: Re: Postgres SQLSTATE[08006] [7] timeout expired