From: | Adrian Klaver <aklaver(at)comcast(dot)net> |
---|---|
To: | pgsql-general(at)postgresql(dot)org |
Cc: | Conrad Lender <crlender(at)gmail(dot)com> |
Subject: | Re: "No transaction in progress" warning |
Date: | 2009-05-07 13:51:36 |
Message-ID: | 200905070651.37036.aklaver@comcast.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Thursday 07 May 2009 3:33:09 am Conrad Lender wrote:
> Hello.
>
> We've recently discovered a bug in our code that resulted in COMMITs
> without BEGINs, and our client saw "no transaction in progress" warnings
> in his log file. What worries me is that we didn't discover this problem
> during development - the warning doesn't show up in our logs. We're both
> using 8.3, and the settings in both postgresql.conf files are similar
> (except for memory settings and file locations).
>
> SHOW log_min_messages;
> log_min_messages
> ------------------
> notice
> (1 row)
>
> I thought this would cause all warnings to be logged automatically. When
> I enter "COMMIT" in psql, I do get the warning, but I don't see it in
> the log file. What could be the problem?
Are you certain you are looking at the correct log file? One way I test is to
run 'select 1/0;' this yields an ERROR.
>
>
> Thanks,
> - Conrad
--
Adrian Klaver
aklaver(at)comcast(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2009-05-07 13:55:17 | Re: Power outage and funny chars in the logs |
Previous Message | David Fetter | 2009-05-07 13:50:11 | Re: prepared statements and DBD::Pg |