On Fri, Nov 16, 2018 at 4:07 AM Kevin Grittner wrote:
>
> On Thu, Nov 15, 2018 at 3:03 AM Kuntal Ghosh
> wrote:
>
> > The test multiple-row-versions is failing because of the
> > above-discussed scenario. I've attached the regression diff file and
> > the result output file for the same. Here
On Thu, Nov 15, 2018 at 3:03 AM Kuntal Ghosh wrote:
> The test multiple-row-versions is failing because of the
> above-discussed scenario. I've attached the regression diff file and
> the result output file for the same. Here is a brief summary of the
> test w.r.t. heap:
>
> Step 1: T1-> BEGIN;
On Thu, Nov 15, 2018 at 3:09 AM Kevin Grittner wrote:
>
> On Wed, Nov 14, 2018 at 5:43 AM Joshua Yanovski
> wrote:
>
> > This is only a personal anecdote, but from my own experience with
> > serializability, this sort of blind update isn't often contended in
> > realistic workloads.
>
> > So,
On Wed, Nov 14, 2018 at 5:13 PM Joshua Yanovski
wrote:
>
> This is only a personal anecdote, but from my own experience with
> serializability, this sort of blind update isn't often contended in realistic
> workloads. The reason is that (again, IME), most blind writes are either
> insertions,
On Wed, Nov 14, 2018 at 5:43 AM Joshua Yanovski
wrote:
> This is only a personal anecdote, but from my own experience with
> serializability, this sort of blind update isn't often contended in realistic
> workloads.
> So, if this only affects transactions with blind updates, I doubt it will
On Tue, Nov 13, 2018 at 10:45 PM Kuntal Ghosh
wrote:
> Currently, we're working on the serializable implementations for
> zheap.
Great!
> If transaction T1 reads a row version (thus acquiring a predicate lock
> on it) and a second transaction T2 updates that row version (thus
> creating a
This is only a personal anecdote, but from my own experience with
serializability, this sort of blind update isn't often contended in
realistic workloads. The reason is that (again, IME), most blind writes
are either insertions, or "read-writes in disguise" (the client read an old
value in a
Hello hackers,
Currently, we're working on the serializable implementations for
zheap. As mentioned in README-SSI documentation[1], there is one
difference in SSI implementation of PostgreSQL that can differentiate
the conflict detection behaviour with other storage engines that
supports updates
