On 2015-03-03 21:49:21 -0500, Robert Haas wrote:
> On Sat, Feb 21, 2015 at 11:34 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> > Andres Freund <andres@2ndquadrant.com> writes:
> >> On 2015-02-20 22:19:54 -0500, Peter Eisentraut wrote:
> >>> On 2/20/15 8:46 PM, Josh Berkus wrote:
> >>>> Or what about just doing CSV?
> >
> >>> I don't think that would actually address the problems. It would just
> >>> be the same format as now with different delimiters.
> >
> >> Yea, we need hierarchies and named keys.
> >
> > Yeah. One thought though is that I don't think we need the "data" layer
> > in your proposal; that is, I'd flatten the representation to something
> > more like
> >
> > {
> > oid => 2249,
> > oiddefine => 'CSTRINGOID',
> > typname => 'cstring',
> > typlen => -2,
> > typbyval => 1,
> > ...
> > }
>
> Even this promises to vastly increase the number of lines in the file,
> and make it harder to compare entries by grepping out some common
> substring. I agree that the current format is a pain in the tail, but
> pg_proc.h is >5k lines already. I don't want it to be 100k lines
> instead.
Do you have a better suggestion? Sure it'll be a long file, but it still
seems vastly superiour to what we have now.
Greetings,
Andres Freund
-- Andres Freund http://www.2ndQuadrant.com/PostgreSQL Development, 24x7 Support, Training &
Services