| From: | John R Pierce <pierce(at)hogranch(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-10 16:51:32 |
| Message-ID: | 4A805014.60401@hogranch.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. 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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David Fetter | 2009-08-10 16:57:06 | Re: Accessing a database form another database |
| Previous Message | Bill Thoen | 2009-08-10 16:48:10 | Accessing a database form another database |