Alvaro Herrera wrote:
Matthew T. O'Connor escribió:
As Alvaro already said this is a case where autovacuum still isn't
great.
While I have your attention ;-) do you have any ideas on how to improve
this? I don't see anything that looks like a solution for this case.
No good ideas,
Matthew T. O'Connor escribió:
> As Alvaro already said this is a case where autovacuum still isn't
> great.
While I have your attention ;-) do you have any ideas on how to improve
this? I don't see anything that looks like a solution for this case.
--
Alvaro Herrera
Chris Hoover wrote:
Another question.
When autovacuum sleeps, does it release the lock it has on the table?
What we would like to have happen is for vacuum to work for a while,
sleep, and while it is sleeping run an analyze on the table. We need
this due to how quickly our data is changing.
Chris Hoover escribió:
> Another question.
>
> When autovacuum sleeps, does it release the lock it has on the table?
What do you mean sleep? There are two sleeps: the one caused by
cost-based vacuum delay (lasts for some milliseconds, happens every
handful of pages vacuumed; no locks released he
Another question.
When autovacuum sleeps, does it release the lock it has on the table?
What we would like to have happen is for vacuum to work for a while, sleep,
and while it is sleeping run an analyze on the table. We need this due to
how quickly our data is changing. Currently we are runnin
On Tue, May 16, 2006 at 02:00:21PM -0400, Chris Hoover wrote:
> Thanks to those who answered my first question. I am looking at
> implementing autovacuuming on our new production 8.1.3 systems. I am
> reading the documentation on the various configuration parameters. The
> autovacuum_analyze_thr
U can install pgstattuple module which is available in the contrib directory and run it on production as
psql> \x
psql> select * from pgstattuple('public'.'tablename');
it displays the table_len, tuple_count, tuple_len, tuple_percent, dead_tuple_count, dead_tuple_len,dead_tuple_percent,free_s
Thanks to those who answered my first question. I am looking at implementing autovacuuming on our new production 8.1.3 systems. I am reading the documentation on the various configuration parameters. The autovacuum_analyze_threshold and autovacuum_vacuum_threshold talk about the number of update
