Re: transaction idle timeout in 7.4.5 and 8.0.0beta2

From: "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Szima G?bor <sygma(at)axelero(dot)hu>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: transaction idle timeout in 7.4.5 and 8.0.0beta2
Date: 2004-09-18 19:50:56
Message-ID: 20040918195056.GA90239@xs4all.nl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Sep 18, 2004 at 03:41:24PM -0400, Tom Lane wrote:
> >> No, stats_command_string need not be set, only stats_start_collector.
>
> > BTW, I've got this set (I'm even running as "postgres") but still I get
> > the "<command string not enabled>" message instead of current_query. :(
>
> It has to be set in the backend you want the info from ...

I set it in /etc/postgresql/postgresql.conf; then I restarted the postmaster
just to be sure, and checked from psql. Same message, even about the same
session:

jtv(at)bulletproof:~$ sudo su postgres -c 'postgresql-8.0/bin/psql template1'
Password:
Welcome to psql 8.0.0beta1, the PostgreSQL interactive terminal.

Type: \copyright for distribution terms
\h for help with SQL commands
\? for help with psql commands
\g or terminate with semicolon to execute query
\q to quit

template1=# select * from pg_stat_activity;
datid | datname | procpid | usesysid | usename | current_query | query_start
-------+-----------+---------+----------+----------+------------------------------+-------------
1 | template1 | 11559 | 1 | postgres | <command string not enabled> |
(1 row)

template1=# show stats_start_collector;
stats_start_collector
-----------------------
on
(1 row)

Jeroen

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2004-09-18 20:05:26 Re: transaction idle timeout in 7.4.5 and 8.0.0beta2
Previous Message Tom Lane 2004-09-18 19:41:24 Re: transaction idle timeout in 7.4.5 and 8.0.0beta2