Re: Complexity of contrib types - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Complexity of contrib types
Date
Msg-id 199807211512.LAA29134@candle.pha.pa.us
Whole thread Raw
In response to Re: Complexity of contrib types  (Hannu Krosing <hannu@trust.ee>)
List pgsql-hackers
> Bruce Momjian <maillist@candle.pha.pa.us> wrote:
> >
> > Doing complex stuff like indexing with contrib stuff is tricky, and one
> > reason we want to move stuff out of there as it becomes popular.  It is
> > just too hard for someone not experienced with the code to implement.
> > Add to this the fact that the oid at the time of contrib installation
> > will change every time you install it, so it is even harder/impossible
> > to automate.
>
> We should develop (or at least prominently promote _and_ document) some
> kind of file/package format or tool (maybe like illustra datablades),
> that would standardize the layout of contrib types.
>
> Also, the need to manually get oids is a real show-stopper.
> A short-time solution would be to develop functions that return these
> oids,
> like get_proc_oid_for(proc_name,arg1_type,arg2_type,...).

Can't they SELECT from pg_proc?

>
> The real solution would of course be extending the (Postgre)SQL language
> to find the OIDs automatically, like Oracle currently does for its
> COMMENT
> statement, an equivalent of which could be used in PostgreSQL to insert
> values in pg_description on the fly.

We return oid's as part of an INSERT.  Is that what you meant?

--
Bruce Momjian                          |  830 Blythe Avenue
maillist@candle.pha.pa.us              |  Drexel Hill, Pennsylvania 19026
  +  If your life is a hard drive,     |  (610) 353-9879(w)
  +  Christ can be your backup.        |  (610) 853-3000(h)

pgsql-hackers by date:

Previous
From: Bruce Momjian
Date:
Subject: Re: [HACKERS] proposals for LLL, part 1
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] cvs and empty directories