Re: Why are there no inequality scans for ctid?

From: Christoph Berg <cb(at)df7cb(dot)de>
To: hubert depesz lubaczewski <depesz(at)depesz(dot)com>
Cc: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>, pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why are there no inequality scans for ctid?
Date: 2013-06-28 13:09:37
Message-ID: 20130628130937.GJ14305@msgid.df7cb.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Re: hubert depesz lubaczewski 2013-06-28 <20130628085246(dot)GA25949(at)depesz(dot)com>
> On Fri, Jun 28, 2013 at 02:21:10PM +0530, Atri Sharma wrote:
> > How would this be helpful for general use cases? Querying on tids on a
> > specific page doesn't seem too useful for any other case than the one
> > you mentioned above, and IMHO it seems to be the job of vacuum.
> > I may be missing something here though.
>
> Vacuum doesn't move rows around (as far as I can tell by running vacuum
> ~ 100 times on bloated table).
>
> And as for general case - sure. It's not really useful aside from bloat
> removal, but I think that bloat removal is important enough to warrant
> some help from Pg.

It would also be useful for querying broken tables where you "SELECT *
FROM badtable WHERE ctid < '(123,0)';" to avoid dying on a bad block.

Christoph
--
cb(at)df7cb(dot)de | http://www.df7cb.de/

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vick Khera 2013-06-28 13:34:55 Re: AFTER triggers and constraints
Previous Message Albe Laurenz 2013-06-28 12:55:11 Re: How to REMOVE an "on delete cascade"?