Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system - Mailing list pgsql-hackers

From Jeff Janes
Subject Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system
Date
Msg-id CAMkU=1yTh2ogYmMkEwGT6uGQ4tktrCXCg8dXpeerURSxMwTsRg@mail.gmail.com
Whole thread Raw
In response to Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system  (Tomas Vondra <tv@fuzzy.cz>)
List pgsql-hackers
On Tue, Feb 5, 2013 at 2:31 PM, Tomas Vondra <tv@fuzzy.cz> wrote:
>
>> We do not already have this.  There is no relevant spec.  I can't see
>> how this could need pg_dump support (but what about pg_upgrade?)
>
> pg_dump - no
>
> pg_upgrage - IMHO it should create the pg_stat directory. I don't think
> it could "convert" statfile into the new format (by splitting it into
> the pieces). I haven't checked but I believe the default behavior is to
> delete it as there might be new fields / slight changes of meaning etc.

Right, I have no concerns with pg_upgrade any more.  The pg_stat will
inherently get created by the initdb of the new cluster (because the
initdb will done with the new binaries with your patch in place them).

pg_upgrade currently doesn't copy over global/pgstat.stat.  So that
means the new cluster doesn't have the activity stats either way,
patch or unpatched.  So if it is not currently a problem it will not
become one under the proposed patch.

Cheers,

Jeff



pgsql-hackers by date:

Previous
From: Vitalii Tymchyshyn
Date:
Subject: Re: [JDBC] JPA + enum == Exception
Next
From: Euler Taveira
Date:
Subject: Re: Fwd: Successful post to pgsql-hackers