Re: Postgres 8.3 archive_command
От | Kevin Grittner |
---|---|
Тема | Re: Postgres 8.3 archive_command |
Дата | |
Msg-id | 474411C9.EE98.0025.0@wicourts.gov обсуждение исходный текст |
Ответ на | Re: Postgres 8.3 archive_command (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Postgres 8.3 archive_command
|
Список | pgsql-hackers |
>>> On Wed, Nov 21, 2007 at 10:57 AM, in message <12172.1195664252@sss.pgh.pa.us>, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Simon Riggs <simon@2ndquadrant.com> writes: >> On Wed, 2007-11-21 at 11:27 -0500, Tom Lane wrote: >>> That would confuse people terribly, and it *would* endanger our ability >>> to see what was happening, 254 times out of 255. > >> That's my feeling too, just wanted to check it still made sense for >> y'all. > > Just to clarify: I don't object to lowering "successfully archived" > messages to DEBUG1, if the field consensus is that it's too chatty. > What I didn't like was the idea of logging some events but not other > identical events. Agreed on the intermittent logging. I don't feel it's too chatty, but on the other hand, I could always change the logging level on the fly if I was investigating a problem, so it wouldn't be much of an inconvenience to switch it if it bugs others. In poking around the logs just now, I noticed one message I'd like to squelch. Run against Milwaukee County's recent log files: grep -c 'PRIMARY KEY will create implicit index' I get this for the last ten full days: /var/pgsql/data/cc/pg_log/postgresql-2007-11-11_000000.log:210 /var/pgsql/data/cc/pg_log/postgresql-2007-11-12_000000.log:14138 /var/pgsql/data/cc/pg_log/postgresql-2007-11-13_000000.log:13250 /var/pgsql/data/cc/pg_log/postgresql-2007-11-14_000000.log:14912 /var/pgsql/data/cc/pg_log/postgresql-2007-11-15_000000.log:11635 /var/pgsql/data/cc/pg_log/postgresql-2007-11-16_000000.log:10774 /var/pgsql/data/cc/pg_log/postgresql-2007-11-17_000000.log:183 /var/pgsql/data/cc/pg_log/postgresql-2007-11-18_000000.log:120 /var/pgsql/data/cc/pg_log/postgresql-2007-11-19_000000.log:12667 /var/pgsql/data/cc/pg_log/postgresql-2007-11-20_000000.log:13992 It's actually pretty hard to find the archive logging amidst all that. The log is next to useless without a grep -v to filter them out. If we're going to pursue the idea further, I guess I should spawn a new thread, but would people consider moving *that* one to DEBUG1? There's an idea I can get behind! -Kevin
В списке pgsql-hackers по дате отправления: