From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>, Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(), |
Date: | 2006-06-12 15:00:07 |
Message-ID: | 200606121500.k5CF07012126@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
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?
The original motivation for the functions was that we already have some
functions like this in the backend, and they are used by pg_dump, so for
completeness someone suggested they should be added, and then we can
decide if pg_dump should use them, but we can revisit all of this.
--
Bruce Momjian http://candle.pha.pa.us
EnterpriseDB http://www.enterprisedb.com
+ If your life is a hard drive, Christ can be your backup. +
From | Date | Subject | |
---|---|---|---|
Next Message | Jim C. Nasby | 2006-06-12 15:08:22 | Re: postgresql and process titles |
Previous Message | Jim C. Nasby | 2006-06-12 14:54:33 | Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), |