The message level is right next to the message, so in this case it is
WARNING. Setting server_min_messages to error would prevent that
message.
---------------------------------------------------------------------------
Laurette Cisneros wrote:
> What "log level" would generate this message and what do I set it to to get
> rid of it?
>
> Thanks,
>
> L.
> On 14 Feb 2003, Robert Treat wrote:
>
> > On Thu, 2003-02-13 at 18:48, Laurette Cisneros wrote:
> > >
> > > Using 7.3.2 now.
> > >
> > > I noticed a slew of messages in my pgsql log like this:
> > > WARNING: COMMIT: no transaction in progress
> > >
> > > I'm wodering if this is related to the fact that there is now an option in
> > > the postgresql.conf file:
> > > autocommit=true
> > >
> > > Did 7.3.2 change the default behavior of the pgsql server in regards to
> > > soloton transactions?
> > >
> > >
> >
> > Pre 7.3.* version issued "NOTICE: COMMIT: no transaction in progress"
> > instead of "WARNING". The different log level is probably why you didn't
> > see it before.
> >
> > Robert Treat
> >
> >
>
> --
> Laurette Cisneros, L.D.
> The Database Group
> (510) 420-3137
> NextBus Information Systems, Inc.
> www.nextbus.com
> ----------------------------------
> "No man is wise enough by himself"
> -- Titus Maccius Plautus
> (254 Bc - 184 BC), Miles Gloriosus
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
>
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
