What is the option that can be used in PostgreSQL to make transactions see rows affected in previous parts of the transaction?

Sharad Jaiswal
Sharad Jaiswal

Posted On: Feb 22, 2018

 

 The SQL standard is defined by four levels of transaction isolation basically regarding three phenomena. The three phenomenon must be prevented between concurrent transactions. The unwanted phenomena are:
  • Phantom read: A transaction that re-executes a query, returning a set of rows that satisfy a search condition and then finds that the set of rows that have been satisfying the condition has changed due to another recently-committed transaction.
  • Non-repeatable read: A transaction that re-reads the data that it has previously read and then finds that data has already been modified by another transaction (that committed since the initial read).
  • Dirty read : A transaction when reads data that is written by a concurrent uncommitted transaction is the dirty read.

 

    Related Questions

    Please Login or Register to leave a response.

    Related Questions

    Postgresql Interview Questions

    List some of the features of Postgresql ?

     Following are some of the features of Postgresql : Object-relational database Support and Extensibility for SQL fle..

    Postgresql Interview Questions

    Put some light on Multi-Version concurrency control?

     MVCC or better known as Multi-version concurrency control is used to avoid unwanted locking of the database. The time ..

    Postgresql Interview Questions

    How are the stats updated in Postgresql?

    It is not that hard as it seems. To get your statistics updated in PostgreSQL a special function called explicit ‘va..