| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "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(), pg_get_typedefault(), pg_get_attrdef(), |
| Date: | 2006-06-12 03:25:03 |
| Message-ID: | 448CDE8F.1070507@commandprompt.com |
| 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?
Well I can't think of a reason to use the functions as a way to deliver
CREATE statements.
Anyone else have thoughts?
Joshua D. Drake
>
> regards, tom lane
>
--
=== The PostgreSQL Company: Command Prompt, Inc. ===
Sales/Support: +1.503.667.4564 || 24x7/Emergency: +1.800.492.2240
Providing the most comprehensive PostgreSQL solutions since 1997
http://www.commandprompt.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Kirkwood | 2006-06-12 03:47:13 | Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), |
| Previous Message | Tom Lane | 2006-06-12 02:54:51 | Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(), |