Search Postgresql Archives

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

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Jaime

2011/5/30 Jaime Casanova <jaime@xxxxxxxxxxxxxxx> wrote:
> On Sun, May 29, 2011 at 4:55 PM, Stefan Keller <sfkeller@xxxxxxxxx> 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?

Thanks for joining the discussion.

I'm only reluctant to do an ANALYZE as part of a perdiodical (hourly)
"check table contents" function.

Such an ANALYZE command is already included in the perdiodical
(nightly) update script which mirrors OpenStreetMap data.

BTW: I've asked before for best parameters over at pgsql-performance
("How to configure a read-only database server?" 19. April 2011) and I
am still happy about any hint.

Yours, Stefan

-- 
Sent via pgsql-general mailing list (pgsql-general@xxxxxxxxxxxxxx)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-general


[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Postgresql Jobs]     [Postgresql Admin]     [Postgresql Performance]     [Linux Clusters]     [PHP Home]     [PHP on Windows]     [Kernel Newbies]     [PHP Classes]     [PHP Books]     [PHP Databases]     [Postgresql & PHP]     [Yosemite]
  Powered by Linux