Re: pgsql: Publish more openly the fact that autovacuum is working for - Mailing list pgsql-committers

From Tom Lane
Subject Re: pgsql: Publish more openly the fact that autovacuum is working for
Date
Msg-id 14244.1216655114@sss.pgh.pa.us
Whole thread Raw
In response to pgsql: Publish more openly the fact that autovacuum is working for  (alvherre@postgresql.org (Alvaro Herrera))
Responses Re: pgsql: Publish more openly the fact that autovacuum is working for
List pgsql-committers
alvherre@postgresql.org (Alvaro Herrera) writes:
> Publish more openly the fact that autovacuum is working for wraparound
> protection.

Now that I look more closely, there are two things I don't like about
this patch:

* it fails to ratchet up MAX_AUTOVAC_ACTIV_LEN to allow for the
additional text

* it produces something like

    autovacuum: VACUUM (to prevent wraparound) foo.bar

I had thought we were generating

    autovacuum: VACUUM foo.bar (to prevent wraparound)

which seems both easier to read and less likely to break any
existing code that might be trying to interpret pg_stat_activity
entries.

            regards, tom lane

pgsql-committers by date:

Previous
From: alvherre@postgresql.org (Alvaro Herrera)
Date:
Subject: pgsql: Publish more openly the fact that autovacuum is working for
Next
From: jbcooley@pgfoundry.org (User Jbcooley)
Date:
Subject: npgsql - Npgsql2: Improve function metadata queries