| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Jeroen T(dot) Vermeulen" <jtv(at)xs4all(dot)nl> |
| 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 20:09:43 |
| Message-ID: | 7465.1095538183@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Jeroen T. Vermeulen" <jtv(at)xs4all(dot)nl> writes:
> 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. :(
Oh, we're talking at cross-purposes. I was saying that you only need
stats_start_collector in order to have a row in pg_stat_activity
indicating that the backend is still there. If you're going to insist
on examining the query column rather than just the PID, then yes you
need stats_command_string.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeroen T. Vermeulen | 2004-09-18 20:13:29 | Re: transaction idle timeout in 7.4.5 and 8.0.0beta2 |
| Previous Message | Oliver Jowett | 2004-09-18 20:09:35 | Re: libpq and prepared statements progress for 8.0 |