Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess

Поиск
Список
Период
Сортировка
От Robert Haas
Тема Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess
Дата
Msg-id CA+TgmoaGp7Pe80_pAdNit+Hh5JShLkkK+wXu3s6f7R7jmKh7uw@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess  (Andres Freund <andres@anarazel.de>)
Ответы Re: [HACKERS] pg_waldump's inclusion of backend headers is a mess  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Список pgsql-hackers
On Tue, Feb 14, 2017 at 2:54 PM, Andres Freund <andres@anarazel.de> wrote:
>> Thoughts, comments, objections, better ideas?
>
> No better ideas.  I'm a bit concerned about declarations needed both by
> normal and xlog related routines, but I guess that can be solved by a
> third header as you did.

Yeah, that doesn't seem bad to me.  I think it's actually fairly
unfortunate that we've just shoved declarations from 3 or 4 or 5
different source files into a single header in many of these cases.  I
think it leads to not thinking clearly about what the dependencies
between the different source files in the index AM stuff is, and
certainly there seems to be some room for improvement there,
especially with regard to gist and gin.  Sorting that out is a bigger
project than I'm prepared to undertake right now, but I think this is
probably a step in the right direction.

>> +++ b/src/include/access/nbtxlog.h
>> @@ -0,0 +1,255 @@
>> +/*-------------------------------------------------------------------------
>> + *
>> + * nbtree.h
>> + *     header file for postgres btree xlog routines
>
> Wrong file name.

Thanks to you and Michael for the reviews.  Committed.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



В списке pgsql-hackers по дате отправления:

Предыдущее
От: Jim Nasby
Дата:
Сообщение: Re: [HACKERS] Improve OR conditions on joined columns (common starschema problem)
Следующее
От: Pavel Stehule
Дата:
Сообщение: Re: [HACKERS] possibility to specify template database for pg_regress