Re: Bootstrap DATA is a pita
От | Robert Haas |
---|---|
Тема | Re: Bootstrap DATA is a pita |
Дата | |
Msg-id | CA+TgmoYj+=Dh13_gtHZc79AFC7iZAYLHwjPHiQ_ct0eBJQ+vrQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Bootstrap DATA is a pita (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: Bootstrap DATA is a pita
Re: Bootstrap DATA is a pita |
Список | pgsql-hackers |
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. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: