From: | Richard Huxton <dev(at)archonet(dot)com> |
---|---|
To: | Rodrick Hales <RHALES(at)mstc(dot)state(dot)ms(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: NOTICE: there is no transaction in progress |
Date: | 2009-08-12 08:01:11 |
Message-ID: | 4A8276C7.1020807@archonet.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Rodrick Hales wrote:
> We have two machines that run a C application that interfaces with a
> Postgres database. They are our development and production machines.
> The version is PostgreSQL 8.3.7 on i686-redhat-linux-gnu, complied by
> GCC gcc (GCC) 4.1.2.20071124 (Red Hat 4.1.2-42) .
>
> On the development machine, I don't get notices and warnings related
> to Postgres SQL commands. COMMIT and ABORT are likely the culprits.
> On the production machine I do.
The message you mention would be to a COMMIT/ROLLBACK being issued
without a BEGIN. I think the setting you are after is probably
client_min_messages (ch 18 of the manuals). One machine is probably set
to NOTICE and one to WARNING.
Some useful commands:
SHOW client_min_messages;
ALTER DATABASE db1 SET client_min_messages = 'WARNING';
ALTER USER u1 SET client_min_messages = ...
--
Richard Huxton
Archonet Ltd
From | Date | Subject | |
---|---|---|---|
Next Message | Ow Mun Heng | 2009-08-12 08:01:16 | Re: Best way to "mask" password in DBLINK |
Previous Message | Magnus Hagander | 2009-08-12 07:56:17 | Re: Best way to "mask" password in DBLINK |