From: george young <gry@ll.mit.edu>
To: pgsql-sql@postgresql.org
Subject: debugging query to put message in pg logfile?
Date: Thu, 4 Mar 2004 15:32:19 -0500
Message-ID: <20040304153219.210f3648.gry@ll.mit.edu> (raw)
[postgresql-7.4RC2, python-2.3.3, PyGreSQL-3.4, SuSE x86 Linux 8.2]
I've started putting debugging queries like:
select "opwin.py: committing step signoff"
in my app, just to have an entry in the postgres logfile. These are
especially helpful in tracking down what piece of code did a 'commit',
since there's nothing to distinguish one from another in the log.
Is there some cheaper (or more appropriate) sql statement that will show
up in the postgres log? I thought I remembered a "message" sql statement
or something like that.
-- George Young
--
"Are the gods not just?" "Oh no, child.
What would become of us if they were?" (CSL)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: gry@ll.mit.edu
Subject: Re: debugging query to put message in pg logfile?
In-Reply-To: <20040304153219.210f3648.gry@ll.mit.edu>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox