Re: Extensions, this time with a patch - Mailing list pgsql-hackers

From Robert Haas
Subject Re: Extensions, this time with a patch
Date
Msg-id AANLkTikrTtvT7m4x2OdDcikhLhOCazsGmXoBHcM7i-vw@mail.gmail.com
Whole thread Raw
In response to Re: Extensions, this time with a patch  (Dimitri Fontaine <dimitri@2ndQuadrant.fr>)
List pgsql-hackers
On Tue, Oct 19, 2010 at 9:07 AM, Dimitri Fontaine
<dimitri@2ndquadrant.fr> wrote:
> Robert Haas <robertmhaas@gmail.com> writes:
>> I don't see why.  I think the real action item here is to remove =>
>> from hstore.
>
> As input, consider that lots of extensions will create types that are
> only a shell at the moment of the CREATE TYPE, and for each of those
> types you will see the (potentially > 1000 lines long) whole SQL script
> dumped on the screen.
>
> In the following script, I've filtered out the scripts, but it's written
> out for each NOTICE message that you see:
>
> dim ~/dev/PostgreSQL/postgresql-extension psql -c "create extension citext;" 2>&1 | egrep 'NOTICE|ERROR'
> NOTICE:  Installing extension 'citext' from '/Users/dim/pgsql/exts/share/contrib/citext.sql', with user data
> NOTICE:  return type citext is only a shell
> NOTICE:  argument type citext is only a shell
> NOTICE:  return type citext is only a shell
> NOTICE:  argument type citext is only a shell

Well, perhaps it's reasonable to suppress NOTICE messages then.  That
particular message could perhaps be quieted, but we probably don't
want to do that with every NOTICE that might occur (e.g. those that
you might get on table creation for sequences, indices, etc.).

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company


pgsql-hackers by date:

Previous
From: Boszormenyi Zoltan
Date:
Subject: Re: plan time of MASSIVE partitioning ...
Next
From: Alvaro Herrera
Date:
Subject: Re: WIP: extensible enums