Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Under what scenarios we use SERIALIZABLE Isolation level? I have seen some answers on website that says, when you want transaction to be completely isolated, we usually go for this.
What i would like to know from your own experience is that, when you’ve used this in your projects/or you’ve seen this to be used in other projects and what was the specific requirement that was not getting fulfilled by other isolation levels?
SERIALIZABLEis useful when you build complex reports which require several queries.In
READ COMMITTEDorREPEATABLE READthe queries could see the changes made between the transaction started and the moment they ran.pg_dump, thePostgreSQLdump utility, starts it job with issuingSET TRANSACTION ISOLATION LEVEL SERIALIZABLE, to guarantee that the state of database being dumped would be that of the moment the utility was run, and the subsequent changes to the database could not interfere with the dump.