Skip site navigation (1) Skip section navigation (2)

Re: Adding column comment to information_schema.columns

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruno Wolff III <bruno(at)wolff(dot)to>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>,Hannu Krosing <hannu(at)tm(dot)ee>, Justin Clift <jc(at)telstra(dot)net>,PostgreSQL Hackers Mailing List <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Adding column comment to information_schema.columns
Date: 2004-07-02 17:04:14
Message-ID: 15873.1088787854@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackers
Bruno Wolff III <bruno(at)wolff(dot)to> writes:
>   Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> wrote:
>> Why are they useful???? If you want PG specific stuff then use the PG 
>> specific catalogs!!!

> The information schema could be used to provide a more stable interface.
> The pg catalog changes from release to release and it would be nice to
> be able to write code which is more future proof.

Isn't this argument self-contradictory?  The reason information_schema
is stable is that it is standard.  If we start hacking it up to add
implementation-specific stuff, then you lose that stability.  You'll
need to consider the PG version when deciding what queries you can
issue, and there will undoubtedly be scenarios where we have to change
or remove columns that we've added to information_schema.  (We do not
whack the system catalogs around without good reason, after all.)

			regards, tom lane

In response to

Responses

pgsql-hackers by date

Next:From: Andrew DunstanDate: 2004-07-02 17:07:32
Subject: Re: compile errors in new PL/Pler
Previous:From: Joshua D. DrakeDate: 2004-07-02 16:48:54
Subject: Re: compile errors in new PL/Pler

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group