Logging problems in PostgreSQL 7.2devel
От | John Summerfield |
---|---|
Тема | Logging problems in PostgreSQL 7.2devel |
Дата | |
Msg-id | Pine.LNX.4.33.0109040827370.20458-100000@dugite.os2.ami.com.au обсуждение исходный текст |
Ответы |
Re: Logging problems in PostgreSQL 7.2devel
Re: Logging problems in PostgreSQL 7.2devel |
Список | pgsql-bugs |
I have postmaster configured to use syslog. Despite this, these messages appear on the terminal from which I start it: 2001-09-03 23:44:37 [26371] DEBUG: recycled transaction log file 0000000000000044 There are many of those. Here are the relevant lines from the configuration: [pgtest@possum pgtest]$ egrep -v '(^#|^$)' /var/share/pgtest/postgresql/pgsql/data/postgresql.conf tcpip_socket = true show_source_port = true shared_buffers = 1024 # 2*max_connections, min 16 wal_files = 4 # range 0-64 wal_sync_method = fsync # fsync or fdatasync or open_sync or open_datasync wal_debug = 0 # range 0-16 log_connections = true log_timestamp = true log_pid = true debug_level = 0 # range 0-16 debug_assertions = true syslog = 2 # range 0-2 [pgtest@possum pgtest]$ Additionally there are many (supposedly suppressed) (apparently) debugging lines printed out on syslog: Sep 3 20:42:10 possum postgres[26215]: [1] DEBUG: connection: host=192.168.1.6:32923 user=summer database=sharetrader Sep 3 20:42:10 possum postgres[26215]: [2] ERROR: index "ijs0101_stocks_info" does not exist Sep 3 20:42:47 possum postgres[26229]: [1] DEBUG: connection: host=192.168.1.6:32924 user=summer database=sharetrader Sep 3 20:42:47 possum postgres[26229]: [2] ERROR: index "ijs0102_trades" does not exist Sep 3 20:42:47 possum postgres[26229]: [3] ERROR: table "tjs0102_trades" does not exist Sep 3 20:42:47 possum postgres[26229]: [4] NOTICE: CREATE TABLE/UNIQUE will create implicit index 'tjs0102_trades_asx_key'for table 'tjs0102_trades' Sep 3 20:44:22 possum postgres[26270]: [1] DEBUG: recycled transaction log file 0000000000000002 Sep 3 20:49:27 possum postgres[26271]: [1] DEBUG: recycled transaction log file 0000000000000003
В списке pgsql-bugs по дате отправления: