From: Rod Taylor <rbt@rbt.ca>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: sailesh@cs.berkeley.edu, "scott.marlowe" <scott.marlowe@ihs.com>
Cc: Shridhar Daithankar <shridhar_daithankar@persistent.co.in>
Cc: PostgreSQL Hackers <pgsql-hackers@postgresql.org>
Subject: Re: Are we losing momentum?
Date: 24 Apr 2003 19:14:02 -0400
Message-ID: <1051226041.48589.9.camel@jester> (raw)
In-Reply-To: <25012.1051223307@sss.pgh.pa.us>
References: <Pine.LNX.4.33.0304230922450.12251-100000@css120.ihs.com>
<bxyadeg1m3j.fsf@datafix.CS.Berkeley.EDU>
<1051189596.46146.24.camel@jester>
<bxyist3k0io.fsf@datafix.CS.Berkeley.EDU>
<25012.1051223307@sss.pgh.pa.us>
On Thu, 2003-04-24 at 18:28, Tom Lane wrote:
> Sailesh Krishnamurthy <sailesh@cs.berkeley.edu> writes:
> > Rod> The INFORMATION_SCHEMA? Out of curiousity, how do they
> > Rod> handle DB2 extensions? Do they create new views in that
> > Rod> schema? Do they ignore them?
>
> > Why extensions, even for things like indexes that aren't in the
> > standard, they create views (SYSCAT.INDEXES, SYSCAT.INDEXAUTH etc.)
> > ...
> > Certainly - it's just that the meaning and number of existing columns
> > and rows in the syscat views are always backward compatible. That
> > includes support of the info schema - for the sql standard features
> > that db2 supports.
>
> > So if there's something new in the catalog tables that is a result of
> > an extension and doesn't appear as a column in the syscat views (or
> > the info schema) then an appropriate column may be added to the view -
> > provided that this doesn't break the info schema compatibility.
>
> Of course, IBM can afford to keep reps on the SQL standards committee to
> make sure that no future spec extension conflicts with the names they've
> used for their additions to INFORMATION_SCHEMA. We, on the other hand,
> could easily get burnt by spec changes.
We could probably get away with adding pg_ views to the information
schema though. For extensions of an existing view, simply inherit the
real view into a pg_ labelled view and add the new columns.
--
Rod Taylor <rbt@rbt.ca>
PGP Key: http://www.rbt.ca/rbtpub.ascAttachments:
signature.asc (application/pgp-signature, 186B) download
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-hackers@postgresql.org
Cc: rbt@rbt.ca, tgl@sss.pgh.pa.us, scott.marlowe@ihs.com, shridhar_daithankar@persistent.co.in
Subject: Re: Are we losing momentum?
In-Reply-To: <1051226041.48589.9.camel@jester>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox