On 3.1.2013 20:33, Magnus Hagander wrote:
> On Thu, Jan 3, 2013 at 8:31 PM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
>> On 3.1.2013 18:47, Heikki Linnakangas wrote:
>>> How about creating the new directory as a direct subdir of $PGDATA,
>>> rather than buried in global? "global" is supposed to contain data
>>> related to shared catalog relations (plus pg_control), so it doesn't
>>> seem like the right location for per-database stat files. Also, if we're
>>> going to have admins manually zapping the directory (hopefully when the
>>> system is offline), that's less scary if the directory is not buried as
>>> deep.
>>
>> That's clearly possible and it's a trivial change. I was thinking about
>> that actually, but then I placed the directory into "global" because
>> that's where the "pgstat.stat" originally was.
> 
> Yeah, +1 for a separate directory not in global.

OK, I moved the files from "global/stat" to "stat".

Tomas

In response to

• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system at 2013-01-03 19:33:35 from Magnus Hagander

Responses

• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system at 2013-02-01 16:19:26 from Alvaro Herrera
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system at 2013-02-02 22:33:10 from Jeff Janes
• Re: PATCH: Split stats file per database WAS: autovacuum stress-testing our system at 2013-02-03 19:46:39 from Jeff Janes

pgsql-hackers by date

Next:	From: Tatsuo Ishii	Date: 2013-01-06 04:07:21
	Subject: Re: too much pgbench init output
Previous:	From: Tomas Vondra	Date: 2013-01-06 03:35:30
	Subject: Re: PATCH: optimized DROP of multiple tables within a transaction