Re: TODO: Add pg_get_acldef(),

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, Hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: TODO: Add pg_get_acldef(),
Date: 2006-08-22 03:40:42
Message-ID: 200608220340.k7M3egZ13813@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Joshua D. Drake wrote:
> Tom Lane wrote:
> > "Joshua D. Drake" <jd(at)commandprompt(dot)com> writes:
> >> Trying to get back on point. What is the scope of work for the TODO
> >> item? Forget everything else I brought up. What is the goal of the
> >> existing TODO?
> >
> > I'm not sure that the TODO item has a reason to live at all, but surely
> > the first item of work for it should be to figure out what its use-case
> > is. If pg_dump isn't going to use these functions, what will?
>
> Well I can't think of a reason to use the functions as a way to deliver
> CREATE statements.
>
> Anyone else have thoughts?

They seem useful because they allow abstract access to system
information without mucking with the system tables.

--
Bruce Momjian bruce(at)momjian(dot)us
EnterpriseDB http://www.enterprisedb.com

+ If your life is a hard drive, Christ can be your backup. +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2006-08-22 03:49:09 Re: COPY view
Previous Message Bruce Momjian 2006-08-22 02:54:47 Re: pgstattuple extension for indexes