Re: statement-level statistics are disabled error (postgresql.conf)

From: "Campano, Troy" <Troy(dot)Campano(at)LibertyMutual(dot)com>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Postgres general mailing list" <pgsql-general(at)postgresql(dot)org>
Subject: Re: statement-level statistics are disabled error (postgresql.conf)
Date: 2004-06-02 16:34:33
Message-ID: 82C3FD729CFA504CA44E7D32BDED411F0A2EF523@lm-exmsg-07.lm.lmig.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

No luck, did 'make distclean', 'configure', 'make', 'make install'.
My configure command was: ./configure --prefix=/postgres/pin01s

Get this as an error still:

insomnia.lmig.com: (pin01s)> psql template1 -Upostgres --host=insomnia
--port=5433

Password:

WARNING: statement-level statistics are disabled because parser,
planner, or executor statistics are on

psql: FATAL: invalid cache id: 30

If I have this in my postgresql.conf I get the error:

log_parser_stats = true

log_planner_stats = true

log_executor_stats = true

log_statement_stats = true

...however, if I comment out the parser, planner, and executor status
like the warning suggests, restart postgresql, the error goes away:

#log_parser_stats = true

#log_planner_stats = true

#log_executor_stats = true

log_statement_stats = true

Could this be related to this bug?

http://archives.postgresql.org/pgsql-patches/2004-05/msg00093.php

I am running 7.4.2:
template1=# SELECT VERSION();

version

------------------------------------------------------------------------
----

PostgreSQL 7.4.2 on i686-pc-linux-gnu, compiled by GCC gcc (GCC) 3.3.2

-----Original Message-----
From: Tom Lane [mailto:tgl(at)sss(dot)pgh(dot)pa(dot)us]
Sent: Wednesday, June 02, 2004 11:19 AM
To: Campano, Troy
Cc: Postgres general mailing list
Subject: Re: [GENERAL] statement-level statistics are disabled error
(postgresql.conf)

"Campano, Troy" <Troy(dot)Campano(at)LibertyMutual(dot)com> writes:

> psql: FATAL: invalid cache id: 30

Is this a locally built copy? If so try a make distclean, reconfigure,

rebuild. I think you have inconsistent compiled files.

regards, tom lane

Responses

Browse pgsql-general by date

  From Date Subject
Next Message DeJuan Jackson 2004-06-02 16:40:40 Re: ORDER BY with plpgsql parameter
Previous Message Stephan Szabo 2004-06-02 16:34:26 Re: ORDER BY with plpgsql parameter