Re: pg_stat directory and pg_stat_statements

From: Fujii Masao <masao(dot)fujii(at)gmail(dot)com>
To: Tomas Vondra <tv(at)fuzzy(dot)cz>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: pg_stat directory and pg_stat_statements
Date: 2014-05-29 03:22:19
Message-ID: CAHGQGwHNcLzkb-65Jo5C2u3UinE6ga9Nq_oeLD1-n7jkyXqJug@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 29, 2014 at 4:55 AM, Tomas Vondra <tv(at)fuzzy(dot)cz> wrote:
> On 28.5.2014 19:52, Fujii Masao wrote:
>> On Thu, May 29, 2014 at 12:37 AM, Peter Geoghegan <pg(at)heroku(dot)com> wrote:
>>> On Wed, May 28, 2014 at 7:01 AM, Fujii Masao <masao(dot)fujii(at)gmail(dot)com> wrote:
>>>> But pg_stat_statements file is saved under $PGDATA/global yet.
>>>> Is this intentional or just oversight?
>>>
>>>
>>> I think it's an oversight.
>>
>> OK, patch attached.
>>
>> I'm afraid that it's not okay to change the file layout in $PGDATA at this beta1
>> stage because that change basically seems to need initdb. Otherwise something
>> like "no such file or directory" error can happen. But in this case what we need
>> to change is only the location of the pg_stat_statements permanent stats file.
>> So, without initdb, the server will not be able to find the
>> pg_stat_statements stats
>> file, but this is not so harmful. Only the problem is that the
>> pg_stat_statements
>> stats which were collected in past would disappear. OTOH, the server can keep
>> running successfully from then and no critical data will not
>> disappear. Therefore
>> I think we can commit this patch even at beta1. Thought?
>
> For HEAD, probably yes. But what about backpatching 9.3?

I think No. So we should not backpatch this to 9.3.

Regards,

--
Fujii Masao

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2014-05-29 03:23:45 Odd uuid-ossp behavior on smew and shearwater
Previous Message Peter Geoghegan 2014-05-29 01:59:23 Ancient bug in formatting.c/to_char()