Search Postgresql Archives
For SELECT statement (just a reading one, no 'FOR UPDATE'), is COMMIT or ROLLBACK preferred?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: For SELECT statement (just a reading one, no 'FOR UPDATE'), is COMMIT or ROLLBACK preferred?
- From: David Wall <d.wall@xxxxxxxxxxxx>
- Date: Sun, 25 Aug 2019 12:09:41 -0700
- User-agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.14; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
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
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]
[Postgresql Jobs]
[Postgresql Admin]
[Postgresql Performance]
[Linux Clusters]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Postgresql & PHP]
[Yosemite]