Re: More graceful handling of invalid log_*_stats conf in 7.4

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Martin Pitt <martin(at)piware(dot)de>
Cc: PostgreSQL Bugs <pgsql-bugs(at)postgresql(dot)org>, evert(at)witelcom(dot)com, James Troup <james(at)nocrew(dot)org>
Subject: Re: More graceful handling of invalid log_*_stats conf in 7.4
Date: 2005-06-02 15:46:28
Message-ID: 14503.1117727188@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Martin Pitt <martin(at)piware(dot)de> writes:
> I found out that activating

> log_parser_stats = true
> log_planner_stats = true
> log_executor_stats = true
> log_statement_stats = true

> in postgresql.conf leads to this bug

This is another manifestation of the 7.4 problem with trying to test
superuser-ness at inappropriate times. We eventually gave up on the
entire concept of "USERLIMIT" variables. I don't think there is any
reasonably practical patch to fix it in 7.4, sorry ...

regards, tom lane

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message pgsql-bugs 2005-06-02 17:47:02 Postgres 7.4.7 hang in async_notify
Previous Message Bruno Wolff III 2005-06-02 13:02:59 Re: BUG #1697: Select getting slower on continously updating data