This is a discussion on debug levels in server within the Pgsql General forums, part of the PostgreSQL category; --> I'm trying to track down a hang in a slony "lock set" command, which creates triggers on a set ...
| |||||||
| Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| 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? Thanks. - DAP ------------------------------------------------------------------------ ---------- David Parker Tazz Networks (401) 709-5130 |
| ||||
| "David Parker" <dparker@tazznetworks.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 ---------------------------(end of broadcast)--------------------------- TIP 4: Don't 'kill -9' the postmaster |