Re: Postgres 8.3 archive_command

From: "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Simon Riggs" <simon(at)2ndquadrant(dot)com>, "Rudolf van der Leeden" <vanderleeden(at)logicunited(dot)com>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Postgres 8.3 archive_command
Date: 2007-11-21 18:29:53
Message-ID: 474424C1.EE98.0025.0@wicourts.gov
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

>>> On Wed, Nov 21, 2007 at 11:24 AM, in message <12760(dot)1195665880(at)sss(dot)pgh(dot)pa(dot)us>,
Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> "Kevin Grittner" <Kevin(dot)Grittner(at)wicourts(dot)gov> writes:
>> 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'
>
> Set log_min_messages higher than NOTICE. Given the current usage of
> NOTICE --- basically they're *all* newbie-annoyance items ---

Done statewide. Thanks for the suggestion.

> I kinda wonder why WARNING isn't the default setting anyway.

Based on what you said above, I wonder, too. Maybe that's something
to consider changing?

-Kevin

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2007-11-21 18:32:59 Re: VACUUM/ANALYZE counting of in-doubt tuples
Previous Message Simon Riggs 2007-11-21 18:27:46 Re: Postgres 8.3 archive_command