Re: Why Postgres doesn't use TID scan?

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Vladimir Ryabtsev <greatvovan(at)gmail(dot)com>, pgsql-performance(at)lists(dot)postgresql(dot)org
Subject: Re: Why Postgres doesn't use TID scan?
Date: 2018-12-18 16:40:04
Message-ID: 20181218164004.eq423wrntg5egxlj@alvherre.pgsql
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On 2018-Dec-17, Tom Lane wrote:

> Queries like yours are kinda sorta counterexamples to that, but pretty
> much all the ones I've seen seem like crude hacks (and this one is not
> an exception). Writing a bunch of code to support them feels like
> solving the wrong problem. Admittedly, it's not clear to me what the
> right problem to solve instead would be.

Yeah, over the years I've confronted several times with situations where
a deletion by ctid (and sometimes updates, IIRC) was the most convenient
way out of. It's not the kind of thing that you'd do with any
frequency, just one-offs. It's always been a bit embarrasing that this
doesn't "work properly". There's always been some way around it, much
slower and less convenient ...

--
Álvaro Herrera https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Patrick Mulrooney 2018-12-19 04:39:36 Increasing parallelism of queries while using file fdw and partitions
Previous Message Mark Kirkwood 2018-12-18 03:10:50 Re: pgbench results arent accurate