Re: Bootstrap DATA is a pita

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Robert Haas <robertmhaas(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: Andres Freund <andres(at)2ndquadrant(dot)com>, Josh Berkus <josh(at)agliodbs(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Bootstrap DATA is a pita
Date: 2015-03-04 14:06:05
Message-ID: 54F7114D.3020400@gmx.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/3/15 9:49 PM, Robert Haas wrote:
>> 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,

I think lines are cheap. Columns are much harder to deal with.

> and make it harder to compare entries by grepping out some common
> substring.

Could you give an example of the sort of thing you wish to do?

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2015-03-04 14:28:03 Re: NULL-pointer check and incorrect comment for pstate in addRangeTableEntry
Previous Message Robert Haas 2015-03-04 14:01:22 Re: POLA violation with \c service=