On Tue, Jan 17, 2017 at 10:54 PM, Neslisah Demirci <neslisah.demirci@xxxxxxxxxxxxx> wrote: > could not serialize access due to read/write dependencies among > transactions > I also add an index to my query and my query's execution plan > don't use seq scan . These two issues are likely to be somewhat related -- if a sequential scan is used, then any write to that table by another connection causes a read-write dependency (a/k/a rw-conflict), which can eventually contribute to a serialization failure. If you can cause narrower access through indexes, you may see a significant drop in the frequency of these serialization failures. You might want to post the query and its execution plan with all the information suggested here (exact pg version, configuration information, machine descriptions, etc.): https://wiki.postgresql.org/wiki/SlowQueryQuestions On the other hand, if you are going to use serializable transactions (or even repeatable read transactions) you should probably be using some framework that can retry the transaction from the start on a serialization failure. You might be interested in this set of examples of how serializable transactions differ from repeatable read: https://wiki.postgresql.org/wiki/SSI And of course, if you haven't already read the fine manual on the topic: https://www.postgresql.org/docs/current/static/mvcc.html -- Kevin Grittner EDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company -- Sent via pgsql-admin mailing list (pgsql-admin@xxxxxxxxxxxxxx) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-admin
