In all likelihood you do not want to do what you described (lock the tables.) You have to have a basic understanding
ofMVCC and transaction isolation levels to determine if the default behavior of mvcc + 'read committed' is sufficient.
Ina lot of cases it is.
Kiriakos
On Mar 18, 2012, at 7:33 PM, Andre Lopes wrote:
> Hi,
>
> I need to do an operation that I will use some SELECT's and get the
> results, but I want to have sure that those tables have not been
> changed with INSERT's or UPDATES during the operation.
>
> Example:
>
> BEGIN OPERATION
> Select field from table1;
> ...
> Select other_field from table2;
> ...
> END OPERATION
>
> How can I lock these tables to assure that the tables are not getting
> INSERTS's or UPDATE's during the operation?
>
> Best Regards,
>
> --
> Sent via pgsql-general mailing list (pgsql-general@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-general
