Denis Gasparin wrote:
> Another question/idea: why don't put messages about what tables got
> vacuumed by the autovacuum daemon as normal log messages (instead of
> debug2)?
We did that for 8.3, actually.
> I think it could be useful because in this way you can also know what
> tables are used m
Alvaro Herrera ha scritto:
>> However i have no idea of what tables the autovacuum daemon is
>> processing because there aren't autovacuum info columns on
>> pg_stat_all_tables (as there are for 8.2.x).
>>
>
> For that, you need to change log_min_messages to debug2.
>
> Keep track of the PID o
Denis Gasparin wrote:
> How is it possibile to check if autovacuum is running in 8.1.x?
>
> "Show Autovacuum" gives me "on" and also i see evidence in logs
> where,autovacuum writes "LOG: autovacuum: processing database ".
Then it is running.
> However i have no idea of what tables the auto
How is it possibile to check if autovacuum is running in 8.1.x?
"Show Autovacuum" gives me "on" and also i see evidence in logs
where,autovacuum writes "LOG: autovacuum: processing database ".
However i have no idea of what tables the autovacuum daemon is
processing because there aren't auto
How is it possibile to check if autovacuum is running in 8.1.x?
"Show Autovacuum" gives me on and also i see evidence in logs where
autovacuum writes "LOG: autovacuum: processing database ".
However i have no idea of what tables the autovacuum daemon is
processing because there aren't autova
"Scott Marlowe" <[EMAIL PROTECTED]> writes:
> So it's a good idea to allocate 20 to 50% more than what vacuum
> verbose says you'll need for overhead. also keep in mind that vacuum
> verbose only tells you what the one db in the server needs.
No, that's not true --- the numbers it prints are clus
Scott Marlowe wrote:
On 8/28/07, Karl Denninger <[EMAIL PROTECTED]> wrote:
Am I correct in that this number will GROW over time? Or is what I see
right now (with everything running ok) all that the system
will ever need?
They will grow at first to accomodate your typical load of de
On 8/28/07, Karl Denninger <[EMAIL PROTECTED]> wrote:
>
> Am I correct in that this number will GROW over time? Or is what I see
> right now (with everything running ok) all that the system
> will ever need?
They will grow at first to accomodate your typical load of dead tuples
created between
Steve Crawford wrote:
Karl Denninger wrote:
Are your FSM settings enough to keep track of the dead space you have?
I don't know. How do I check?
vacuum verbose;
Toward the bottom you will see something like:
...
1200 page slots are required to track all free space.
Current
Tom Lane wrote:
Karl Denninger <[EMAIL PROTECTED]> writes:
But... .shouldn't autovacuum prevent this? Is there some way to look in
a log somewhere and see if and when the autovacuum is being run - and on
what?
There's no log messages (at the default log verbosity anyway). But you
co
Karl Denninger wrote:
>> Are your FSM settings enough to keep track of the dead space you have?
>>
> I don't know. How do I check?
vacuum verbose;
Toward the bottom you will see something like:
...
1200 page slots are required to track all free space.
Current limits are: 453600 page slots, 100
Karl Denninger <[EMAIL PROTECTED]> writes:
> But... .shouldn't autovacuum prevent this? Is there some way to look in
> a log somewhere and see if and when the autovacuum is being run - and on
> what?
There's no log messages (at the default log verbosity anyway). But you
could look into the pg_
I don't know. How do I check?
Karl Denninger ([EMAIL PROTECTED])
http://www.denninger.net
Alvaro Herrera wrote:
Karl Denninger wrote:
A manual "Vacuum full analyze" fixes it immediately.
But... .shouldn't autovacuum prevent this? Is there some way to look in a
log somewhere and see
Karl Denninger wrote:
> A manual "Vacuum full analyze" fixes it immediately.
>
> But... .shouldn't autovacuum prevent this? Is there some way to look in a
> log somewhere and see if and when the autovacuum is being run - and on
> what?
Are your FSM settings enough to keep track of the dead spa
Running 8.2.4.
The following is in my postgresql.conf:
# - Query/Index Statistics Collector -
#stats_command_string = on
update_process_title = on
stats_start_collector = on # needed for block or row stats
# (change requires restart)
#stats_b
15 matches
Mail list logo
