From: | "Andrew Dunstan" <andrew(at)dunslane(dot)net> |
---|---|
To: | "PostgreSQL Hackers Mailing List" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | logging dbname |
Date: | 2003-08-02 21:24:56 |
Message-ID: | 003c01c3593c$86a33aa0$6401a8c0@DUNSLANE |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
So far I have a regression check run that generates a postmaster log that looks like this:
LOG: database system was shut down at 2003-08-02 16:39:48 EDT
LOG: checkpoint record is at 0/9A0530
LOG: redo record is at 0/9A0530; undo record is at 0/0; shutdown TRUE
LOG: next transaction id: 534; next oid: 17139
LOG: database system is ready
[db:regression] ERROR: group "regressgroup1" does not exist
[db:regression] ERROR: value too long for type character(1)
[db:regression] ERROR: value too long for type character(4)
.
.
.
[db:regression] NOTICE: drop cascades to table c1
[db:regression] NOTICE: drop cascades to constraint p1_a1 on table c1
[db:regression] NOTICE: drop cascades to table foo column f2
LOG: received smart shutdown request
LOG: shutting down
LOG: database system is shut down
At the moment it's forced, so the next thing would be to make it a GUC variable (log_dbname?).
Thoughts on format, location of name, etc?
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Jenny - | 2003-08-02 21:27:51 | locking granularity |
Previous Message | Carlos Guzman Alvarez | 2003-08-02 21:19:31 | Identification of serial fields |