X-Original-To: pgsql-hackers-postgresql.org@localhost.postgresql.org
Received: from localhost (unknown [200.46.204.144])
	by svr1.postgresql.org (Postfix) with ESMTP id 705DAD1B1D2
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Thu,  1 Jul 2004 23:51:59 -0300 (ADT)
Received: from svr1.postgresql.org ([200.46.204.71])
	by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024)
	with ESMTP id 39267-07
	for <pgsql-hackers-postgresql.org@localhost.postgresql.org>;
	Fri,  2 Jul 2004 02:52:00 +0000 (GMT)
Received: from mako1.telstra.net (mako1.telstra.net [203.50.0.28])
	by svr1.postgresql.org (Postfix) with ESMTP id 749C7D1B1CD
	for <pgsql-hackers@postgresql.org>;
	Thu,  1 Jul 2004 23:51:54 -0300 (ADT)
Received: from telstra.net (xena.telstra.net [203.50.0.233])
	by mako1.telstra.net (8.12.9/8.11.1) with ESMTP id i622psB4078705;
	Fri, 2 Jul 2004 12:51:55 +1000 (EST) (envelope-from jc@telstra.net)
Message-ID: <40E4CD85.1040000@telstra.net>
Date: Fri, 02 Jul 2004 12:50:45 +1000
From: Justin Clift <jc@telstra.net>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4.1) Gecko/20040406
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Greg Sabino Mullane <greg@turnstep.com>
Cc: pgsql-hackers@postgresql.org
Subject: Re: Adding column comment to information_schema.columns
References: <270f2a128cf161491a34c16ee00b082e@biglumber.com>
In-Reply-To: <270f2a128cf161491a34c16ee00b082e@biglumber.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
X-Virus-Scanned: by amavisd-new at hub.org
X-Spam-Status: No, hits=0.0 tagged_above=0.0 required=5.0 tests=
X-Spam-Level: 
X-Archive-Number: 200407/78
X-Sequence-Number: 55639

Greg Sabino Mullane wrote:
<snip>
> If there is that much clamor for this, why not make a new schema,
> such as "pginformation_schema" People could then tweak the views
> to their heart's content, while keeping 100% compliance.

Doesn't sound very neat.

If we add a pginformation_schema, then it'd probably contain all of the 
existing information_schema... plus more.  Reduplication?

I guess we could just leverage off the existing information_schema views:

i.e.

CREATE VIEW pg_information_schmema.some_view AS SELECT * FROM 
information_schema.some_view (then add extra bits).

But it still doesn't sound very neat.

?

Regards and best wishes,

Justin Clift