From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> |
Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us> |
Subject: | Re: release notes: tids & self-joins |
Date: | 2019-06-13 21:19:48 |
Message-ID: | 19130.1560460788@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Rowley <david(dot)rowley(at)2ndquadrant(dot)com> writes:
> On Fri, 14 Jun 2019 at 05:22, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> Robert Haas <robertmhaas(at)gmail(dot)com> writes:
>>> So I think that this should probably be changed to say something like
>>> "Improve optimization of self-joins on ctid columns" or "Improve
>>> optimization of joins involving columns of type tid."
>> The latter seems fine to me.
> The latter seems a bit inaccurate to me given the fact that a column
> with the type tid could exist elsewhere in the table. Perhaps
> "columns of type tid" can be swapped with "a table's ctid column".
It's true that the parameterized-tidscan patch only helps for joins
to CTID, but the other patch helps for joins to any tid column.
So I still say Robert's wording is fine.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2019-06-13 21:32:14 | pgsql: Avoid spurious deadlocks when upgrading a tuple lock |
Previous Message | David Rowley | 2019-06-13 20:53:05 | Re: release notes: tids & self-joins |