pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: Vladimir Ryabtsev <greatvovan@gmail.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: Why Postgres doesn't use TID scan?
Date: Tue, 18 Dec 2018 13:40:04 -0300
Message-ID: <20181218164004.eq423wrntg5egxlj@alvherre.pgsql> (raw)
In-Reply-To: <31790.1545097237@sss.pgh.pa.us>

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




view thread (11+ messages)  latest in thread

Message-ID: <20181218164004.eq423wrntg5egxlj@alvherre.pgsql>
Permalink:  ../20181218164004.eq423wrntg5egxlj@alvherre.pgsql/
Also on:    postgresql.org/message-id/20181218164004.eq423wrntg5egxlj@alvherre.pgsql

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: alvherre@2ndquadrant.com, tgl@sss.pgh.pa.us, greatvovan@gmail.com, pgsql-performance@lists.postgresql.org
  Subject: Re: Why Postgres doesn't use TID scan?
  In-Reply-To: <20181218164004.eq423wrntg5egxlj@alvherre.pgsql>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox