"Tao Ma" <[email protected]> writes:
> But if I wanna check the parameter informations, it's a little hard to
> read. If I wanna write a program to re-construct the procedure source
> code, it is not convenience to access the parameter informations from
> the front-end. What cons are there If store the procedure and its
> parameters in different tables(e.g. pg_attribute and pg_attrdef)?
Loss of backwards compatibility, for one thing. We're not going to
redesign those catalogs just because somebody thinks some other layout
would be more convenient for one purpose --- it would break a lot of
code for little gain.
regards, tom lane
--
Sent via pgsql-hackers mailing list ([email protected])
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
