From: | Shoaib Mir <shoaibmir(at)gmail(dot)com> |
---|---|
To: | John R Pierce <pierce(at)hogranch(dot)com> |
Cc: | Rodrick Hales <RHALES(at)mstc(dot)state(dot)ms(dot)us>, pgsql-general(at)postgresql(dot)org |
Subject: | Re: NOTICE: there is no transaction in progress |
Date: | 2009-08-10 23:41:27 |
Message-ID: | bf54be870908101641x48cb5247yf8ade38b75a7f581@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Tue, Aug 11, 2009 at 2:51 AM, John R Pierce <pierce(at)hogranch(dot)com> wrote:
> 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. I
>> understand these errors get sent to the 'stderr' stream by default. I don't
>> know which command exactly is causing the notices and warnings in the
>> program and why the behavior is only happening on one machine. Are there
>> some settings on the database that have been set for displaying such
>> warnings and notices? Why does it happen one and not the other? Any
>> suggestions would be greatly appreciated. Thanks.
>>
>>
>
>
> logging is controlled by various settings in postgresql.conf
>
Best is to go through the manual at -->
http://www.postgresql.org/docs/8.3/static/runtime-config-logging.html
and then take a difference of settings between the two.
--
Shoaib Mir
http://shoaibmir.wordpress.com/
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Headland | 2009-08-11 00:52:36 | Updating a specific number of rows in pl/pgsql |
Previous Message | Kobus Wolvaardt | 2009-08-10 22:24:48 | Re: Accessing a database form another database |