Postgres Pro
Downloads
Home   >   mailing lists

Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(), - Mailing list pgsql-hackers

From Tom Lane
Subject Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),
Date
Msg-id 29689.1150080891@sss.pgh.pa.us
Whole thread Raw
In response to Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),  ("Joshua D. Drake" <jd@commandprompt.com>)
Responses Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),  ("Joshua D. Drake" <jd@commandprompt.com>)
Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Tree view 
"Joshua D. Drake" <jd@commandprompt.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?
        regards, tom lane

pgsql-hackers by date:

Previous
From: Kris Kennaway
Date:
Subject: Re: postgresql and process titles
Next
From: "Joshua D. Drake"
Date:
Subject: Re: TODO: Add pg_get_acldef(), pg_get_typedefault(), pg_get_attrdef(),