Re: Queries getting older values (autocommit enabled)
От | Eudald Valcàrcel Lacasa |
---|---|
Тема | Re: Queries getting older values (autocommit enabled) |
Дата | |
Msg-id | CANEx+AVS4a7PYUV3ERfcfipqY_=Yz6y3tP1U0RE6n4Pe=eQS3w@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Queries getting older values (autocommit enabled) (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Queries getting older values (autocommit enabled)
|
Список | pgsql-bugs |
Hello!
Thanks David and Tom for your answer.
I'll check out mvcc. Would user defined locks on a specific table make PostgreSql underperform too much?
Thanks again,
Eudald
El vie., 24 abr. 2020 a las 18:15, Tom Lane (<tgl@sss.pgh.pa.us>) escribió:
Eudald Valcàrcel Lacasa <eudald.valcarcel@gmail.com> writes:
> Could it be possible that, somehow, the select query starts before the
> update one, although it's printed as if it's being executed after it?
It's certainly possible that the select is using a snapshot that was
taken before the update commits. You should read this chapter of
the manual for background and some hints:
https://www.postgresql.org/docs/current/mvcc.html
regards, tom lane
В списке pgsql-bugs по дате отправления: