Re: Index tuple deduplication limitations in pg13

From: Peter Geoghegan <pg(at)bowt(dot)ie>
To: Matthias van de Meent <matthias(dot)vandemeent(at)cofano(dot)nl>
Cc: pgsql-general General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Index tuple deduplication limitations in pg13
Date: 2020-08-18 21:01:30
Message-ID: CAH2-Wz=qUVYiJtj1EB7WzMOnu1SdeWZkHa_fArwMz8sJYfDZQA@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Tue, Aug 18, 2020 at 1:31 PM Matthias van de Meent
<matthias(dot)vandemeent(at)cofano(dot)nl> wrote:
> Would this extra ordering not effectively be an extra tiebreaker in
> the ordering, applied before the TID? I do not know the full
> implications of that, but I believe that would not result in the
> limitations that you are mentioning.

You could probably do it that way, but again you end up with a lot of
new complexity. Not to mention overhead that would have to be paid by
everyone. It would require code that supported the old way (even if it
was added to Postgres 13) for pg_upgrade, that would also be hard to
test. And it might defeat certain future optimizations based on heap
TID being the only tiebreaker. Having two types of equality might have
to bleed into the optimizer.

It's a question of engineering trade-offs. I don't think that it's worth it.

--
Peter Geoghegan

In response to

Browse pgsql-general by date

  From Date Subject
Next Message David Gallagher 2020-08-19 00:02:16 Re: "Go" (lang) standard driver
Previous Message Adrian Klaver 2020-08-18 20:44:29 Re: Orphaned relations after crash/sigkill during CREATE TABLE