DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma;
	h=mime-version:in-reply-to:references:date:message-id:subject:from:to
	:cc:content-type:content-transfer-encoding;
	b=AX3umJXKUV5I2n7DWlVGnwcWhzOgR/eH58gdl1s2cLxnyN1pbrUKR6eu4PD8jhKVj2
	Jz0aQkD842rsdNrrXvXA2LaNbHL4YzTzZShOzhsN3/Yw6KFiqimLM2CJO9Pu+ZTgVVl6
	DSiOQQej66eOI+VG+AXDT0BMcguJ2omEbp5T8=
MIME-Version: 1.0
In-Reply-To: <4A242CC4.5000400@obviously.com>
References: <4A242CC4.5000400@obviously.com>
Date: Mon, 1 Jun 2009 14:07:35 -0600
Message-ID: <dcc563d10906011307x3ebad394x73bfe6f13bc7d84e@mail.gmail.com>
Subject: Re: Avoiding "will create implicit index" NOTICE
From: Scott Marlowe <scott.marlowe@gmail.com>
To: Bryce Nesbitt <bryce2@obviously.com>
Cc: sql pgsql <pgsql-sql@postgresql.org>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

On Mon, Jun 1, 2009 at 1:32 PM, Bryce Nesbitt <bryce2@obviously.com> wrote:
> I'm looking for a good way to avoid triggering the "will create implicit
> index" NOTICE that Postgres (all versions) puts out. =A0This ends up spam=
ming
> cron scripts for no good reason:
>
> =3D> create table junk_six (foo int, primary key (foo));
> NOTICE: =A0CREATE TABLE / PRIMARY KEY will create implicit index
> "junk_six_pkey" for table "junk_six"
> CREATE TABLE
>
> I've got a hacky solution (in perl), pulled from
> =A0http://www.perlmonks.org/index.pl/jacques?node_id=3D540511
> which suppresses the warning:
>
> my $tmpwarn =3D $SIG{__WARN__};
> $SIG{__WARN__} =3D sub { print STDERR @_ if $_[0] !~ m/NOTICE: =A0CREATE =
TABLE/;
> };
> $sqldb->sql_execute("create table junk_six (foo int, primary key (foo));"=
);
> $SIG{__WARN__} =3D $tmpwarn;
>
> And I know that I can edit the warning level in postgresql.conf with some
> other side effects.
> But the best solution would be to avoid the notice in the first place. =
=A0Is
> this possible?

You can also set log_min_messages by the connection, by the user, and
by the database.

alter user bubba set log_min_messages=3Derror;

etc.