| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com>, Peter Eisentraut <peter_e(at)gmx(dot)net> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 15:08:07 |
| Message-ID: | 54F71FD7.7060206@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/04/2015 09:51 AM, Robert Haas wrote:
> On Wed, Mar 4, 2015 at 9:06 AM, Peter Eisentraut <peter_e(at)gmx(dot)net> wrote:
>>> 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?
> e.g. grep for a function name and check that all the matches have the
> same volatility.
>
I think grep will be the wrong tool for this format, but if we're
settling on a perl format, a few perl one-liners should be able to work
pretty well. It might be worth shipping a small perl module that
provided some functions, or a script doing common tasks (or both).
cheers
andrew
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2015-03-04 15:10:20 | Re: Question about lazy_space_alloc() / linux over-commit |
| Previous Message | Stephen Frost | 2015-03-04 15:07:12 | Re: Bootstrap DATA is a pita |