Обсуждение: BUG #5930: Increasing log level to debug5 database not working

The following bug has been logged online:

Bug reference:      5930
Logged by:          thiruppathi
Email address:      tgandhi@prion-group.com
PostgreSQL version: 9.0
Operating system:   windows server standard
Description:        Increasing log level to debug5 database not working
Details:

If i increase log level to debug5 in postgresql.conf file my database
connection not working i am getting error like follows so please give me
solution or any thing i should do for recover this problem.

 forked new backend, pid=2720 socket=744
2011-03-15 16:27:51 CET DEBUG:  postgres child[2720]: starting with (
2011-03-15 16:27:51 CET DEBUG:      postgres
2011-03-15 16:27:51 CET DEBUG:      1Unified
2011-03-15 16:27:51 CET DEBUG:  )
2011-03-15 16:27:51 CET DEBUG:  InitPostgres
2011-03-15 16:27:51 CET DEBUG:  my backend id is 3
2011-03-15 16:27:51 CET DEBUG:  StartTransaction
2011-03-15 16:27:51 CET DEBUG:  name: unnamed; blockState:       DEFAULT;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:27:52 CET DEBUG:  received password packet
2011-03-15 16:27:52 CET DEBUG:  CommitTransaction
2011-03-15 16:27:52 CET DEBUG:  name: unnamed; blockState:       STARTED;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:27:52 CET DEBUG:  StartTransactionCommand
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:27:52 CET DEBUG:  StartTransaction
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:27:52 CET DEBUG:  name: unnamed; blockState:       DEFAULT;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:27:52 CET DEBUG:  CommitTransactionCommand
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:27:52 CET DEBUG:  CommitTransaction
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:27:52 CET DEBUG:  name: unnamed; blockState:       STARTED;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:27:52 CET STATEMENT:  select oid, typbasetype from pg_type
where typname = 'lo'
2011-03-15 16:28:01 CET DEBUG:  StartTransaction
2011-03-15 16:28:01 CET DEBUG:  name: unnamed; blockState:       DEFAULT;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:28:01 CET DEBUG:  CommitTransaction
2011-03-15 16:28:01 CET DEBUG:  name: unnamed; blockState:       STARTED;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:28:01 CET DEBUG:  StartTransaction
2011-03-15 16:28:01 CET DEBUG:  name: unnamed; blockState:       DEFAULT;
state: INPROGR, xid/subid/cid: 0/1/0, nestlvl: 1, children:
2011-03-15 16:28:01 CET DEBUG:  CommitTransaction

"thiruppathi" <tgandhi@prion-group.com> wrote:

> If i increase log level to debug5 in postgresql.conf file my
> database connection not working

What do you mean by that?  What do you try to do?  What do you
expect to happen?  What actually happens?  (Copy and paste of
statements and results is good.)

> i am getting error like follows
>
> [many DEBUG level messages]

You configured for logging of a lot of DEBUG messages, and you're
getting them.  I'm not clear on what you think is a problem.

> please give me solution or any thing i should do for recover this
> problem.

If you don't want to log the DEBUG messages you could change your
logging configuration back.

-Kevin