Bruno Wolff III <bruno@wolff.to> writes:
> Christopher Kings-Lynne <chriskl@familyhealth.com.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