| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "David Parker" <dparker(at)tazznetworks(dot)com> |
| Cc: | "postgres general" <pgsql-general(at)postgresql(dot)org> |
| Subject: | Re: debug levels in server |
| Date: | 2005-04-22 05:50:30 |
| Message-ID: | 26969.1114149030@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
"David Parker" <dparker(at)tazznetworks(dot)com> writes:
> I'm trying to track down a hang in a slony "lock set" command, which
> creates triggers on a set of tables. I assume that it's getting blocked
> by a lock on a table somewhere, and I'd like to print out all the
> "create trigger" statements in the postgres log.
>
> I have log_min_messages = DEBUG5, and I'm seeing a lot of logging, but I
> don't see the create trigger statements showing up in the log. What do I
> need to set to get this output?
log_statement ...
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-04-22 06:16:34 | Re: Waiting for Disconnect |
| Previous Message | Dinesh Pandey | 2005-04-22 05:30:02 | How to install Postgres that supports 64-bit integer/date-time. |