| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
| Cc: | Andrew Dunstan <andrew(at)dunslane(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, 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-06 22:25:14 |
| Message-ID: | 20150306222514.GH3291@alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Robert Haas wrote:
> On Wed, Mar 4, 2015 at 2:27 PM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> wrote:
> > BTW one solution to the merge problem is to have unique separators for
> > each entry. For instance, instead of
> Speaking from entirely too much experience, that's not nearly enough.
> git only needs 3 lines of context to apply a hunk with no qualms at
> all, and it'll shade that to just 1 or 2 with little fanfare. If your
> pg_proc entries are each 20 lines long, this sort of thing will
> provide little protection.
Yeah, you're right. This is going to be a problem, and we need some
solution for it. I'm out of ideas, other than of course getting each
entry to be at most two lines long which nobody seems to like (for good
reasons.)
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2015-03-06 22:57:53 | Re: alter user/role CURRENT_USER |
| Previous Message | Alvaro Herrera | 2015-03-06 22:16:21 | Re: Add more tests on event triggers |