Re: pg_get_domaindef

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andrew Dunstan <andrew(at)dunslane(dot)net>, FAST PostgreSQL <fastpgs(at)fast(dot)fujitsu(dot)com(dot)au>, Neil Conway <neilc(at)samurai(dot)com>, pgsql-patches(at)postgresql(dot)org
Subject: Re: pg_get_domaindef
Date: 2007-01-25 05:33:41
Message-ID: 14613.1169703221@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Bruce Momjian <bruce(at)momjian(dot)us> writes:
> Tom Lane wrote:
>> ... convincing use-case that will justify the maintenance load we
>> are setting up for ourselves. "Somebody might want this" is not
>> adequate.

> I realize it is problem to have the function in two places in our code,
> but if we don't make a user-accessible version, every application has to
> roll their own version and update it for our system catalog changes.

Nope, wrong, you are assuming the conclusion. Exactly which apps have
to have this?

regards, tom lane

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Gavin Sherry 2007-01-25 06:23:19 Re: pg_get_domaindef
Previous Message Tom Lane 2007-01-25 05:31:32 Re: [pgsql-patches] unprivileged contrib and pl install

Browse pgsql-patches by date

  From Date Subject
Next Message Gavin Sherry 2007-01-25 06:23:19 Re: pg_get_domaindef
Previous Message Tom Lane 2007-01-25 05:31:32 Re: [pgsql-patches] unprivileged contrib and pl install