| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Niclas Gustafsson" <niclas(dot)gustafsson(at)codesense(dot)com> |
| Cc: | pgsql-admin(at)postgresql(dot)org |
| Subject: | Re: PG_XLOG grows and grows |
| Date: | 2002-05-15 15:37:17 |
| Message-ID: | 8768.1021477037@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
"Niclas Gustafsson" <niclas(dot)gustafsson(at)codesense(dot)com> writes:
> Yes, I know that, I would like to know what commands the client
> has issued sofar in the transaction as this would help us to
> track down if there is some problems in the client, and which
> client that is stalling ( As we have a bunch of different clients
> Working towards the database).
Turn on debug_print_query, log_pid, log_timestamp, and perhaps
log_connections in postgresql.conf. The postmaster log will then
provide a pretty effective trace of what's going on.
BTW, in 7.2 you need to SIGHUP the postmaster after changing
postgresql.conf. I forget whether 7.1 expected that or not.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Niclas Gustafsson | 2002-05-15 16:17:13 | Re: PG_XLOG grows and grows |
| Previous Message | Tom Lane | 2002-05-15 15:15:12 | Re: PG_XLOG grows and grows |