Re: Why are there no inequality scans for ctid?

From: Atri Sharma <atri(dot)jiit(at)gmail(dot)com>
To: depesz(at)depesz(dot)com
Cc: pgsql-general <pgsql-general(at)postgresql(dot)org>
Subject: Re: Why are there no inequality scans for ctid?
Date: 2013-06-28 08:51:10
Message-ID: CAOeZVifc64WFyga8xXh36Pmk7Ai+V42pYvz3ESuuc0TJqs-16Q@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Fri, Jun 28, 2013 at 2:07 PM, hubert depesz lubaczewski
<depesz(at)depesz(dot)com> wrote:
> Hi,
> while working on removing bloat from some table, I had to use ltos of
> logic simply because there are no (idnexable) inequality scans for
> ctids.
>
> Is it because just noone thought about adding them, or are there some
> more fundamental issues?
>
> I could imagine that things like:
>
> select * from table where ctid @ '123' could return all rows from 123rd
> page, or I could:
> select * from table where ctid >= '(123,0)' and ctid < '(124,0)';
>
> Having such operators work would greatly improve bloat reducing
> options.

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.

Regards,
Atri

--
Regards,

Atri
l'apprenant

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message hubert depesz lubaczewski 2013-06-28 08:52:46 Re: Why are there no inequality scans for ctid?
Previous Message hubert depesz lubaczewski 2013-06-28 08:37:57 Why are there no inequality scans for ctid?