| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: WIP patch for parameterized inner paths |
| Date: | 2012-01-25 20:24:59 |
| Message-ID: | 34BEA5FD-6882-46FD-8DB2-0C8612FAF2E2@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Jan 25, 2012, at 12:19 PM, Tom Lane wrote:
>> Why not create a branch? IIRC the build farm can be configured to run branches.
>
> I already know what the patch does against the regression tests.
> Buildfarm testing is not of interest here. What would be of help is,
> say, Kevin volunteering to load up his Circuit Courts software and data
> into a git-head server and see how performance looks with and without
> the patch. Distribution of the code doesn't strike me as being the
> bottleneck.
Yeah, but it would be easier to keep a branch up-to-date via `git rebase` than to maintain the patch, I would think. And if it’s a remote branch, then simpler distribution is a bonus.
Best,
David
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Marko Kreen | 2012-01-25 20:29:32 | Re: GUC_REPORT for protocol tunables was: Re: Optimize binary serialization format of arrays with fixed size elements |
| Previous Message | Tom Lane | 2012-01-25 20:19:34 | Re: WIP patch for parameterized inner paths |