Re: How to check a table content efficiently? With LIMIT and OFFSET?

From: Jaime Casanova <jaime(at)2ndquadrant(dot)com>
To: Stefan Keller <sfkeller(at)gmail(dot)com>
Cc: Alban Hertroys <dalroi(at)solfertje(dot)student(dot)utwente(dot)nl>, Craig Ringer <craig(at)postnewspapers(dot)com(dot)au>, pgsql-general List <pgsql-general(at)postgresql(dot)org>
Subject: Re: How to check a table content efficiently? With LIMIT and OFFSET?
Date: 2011-05-30 01:26:54
Message-ID: BANLkTim1J7S+aokd7kfS486jWmnn=auw1A@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Sun, May 29, 2011 at 4:55 PM, Stefan Keller <sfkeller(at)gmail(dot)com> wrote:
>
>>> 2. There's an autovacuum background process which already does the
>>> job, doesn't it?
>>
>> Yes, but in its own time. If you know there has been a batch of inserts/deletes you might as well run analyse immediately on that table.
>
> My table is a read-only table after all.
> That's another reason why I'm reluctant using ANALYZE <table>.
>

sorry, i don't follow that... why do you think that a read-only table
doesn't need an ANALYZE?

--
Jaime Casanova         www.2ndQuadrant.com
Professional PostgreSQL: Soporte y capacitación de PostgreSQL

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Greg Smith 2011-05-30 01:31:00 Re: Regular disk activity of an idle DBMS
Previous Message Scott Marlowe 2011-05-30 00:46:16 Re: max_connections proposal