Vacuum as "easily obtained" locks

Поиск
Список
Период
Сортировка
От Michael Graham
Тема Vacuum as "easily obtained" locks
Дата
Msg-id 1312364844.24461.48.camel@brutus
обсуждение исходный текст
Ответы Re: Vacuum as "easily obtained" locks
Re: Vacuum as "easily obtained" locks
Список pgsql-general
Hi all,

I have an application that is reading from a queue table, as part of my
testing I stressed the table to check performance, but after the test
was completed I have the a very large empty table:

SELECT relname, pg_size_pretty(pg_relation_size(oid)) AS size,
reltuples::bigint FROM pg_class;

          relname           |   size   | reltuples
----------------------------+----------+-----------
 logdata5queue              | 142 GB   |         0

From reading the documentation I see that postgres would return this
space to that system after a normal vacuum if "one or more pages at the
end of a table become entirely free and an exclusive table lock can be
easily obtained".

What does "easily obtained" mean in this context?  Would my applications
constant polling of the queue mean that the lock could not be easily
obtained?

Cheers,
--
Michael Graham <mgraham@bloxx.com>



В списке pgsql-general по дате отправления: