From: | Peter Geoghegan <pg(at)heroku(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: BTREE_BUILD_STATS build is broken |
Date: | 2016-05-24 03:40:11 |
Message-ID: | CAM3SWZR6ZfnuCWytOPSKWtknuQ3EPC0ehSsvTa+bN0vep0pJXg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 23, 2016 at 8:09 PM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Does it appear to compile without that?
It does. The only thing that's absent is the pgrminclude directive,
which is of course just a C comment.
> (More generally, is there a better answer for that problem?)
My unpublished parallel B-Tree index build patch will move everything
to do with index builds into nbtsort.c. So, I will more than likely
eventually propose that everything in question live there. I think
that's a better approach in general, because the current high-level
coordination from nbtree.c (e.g. how spools are initialized there)
seems a little contrived. A single entry point for nbtsort.c works
better.
Short term, I guess the best solution is to just have a pgrminclude
directive in both files.
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Craig Ringer | 2016-05-24 04:02:15 | Re: PATCH: Batch/pipelining support for libpq |
Previous Message | Craig Ringer | 2016-05-24 03:30:49 | Re: Inheritance |