Re: building pg_dump doesn't work
| От | Tom Lane |
|---|---|
| Тема | Re: building pg_dump doesn't work |
| Дата | |
| Msg-id | 1335.1236179485@sss.pgh.pa.us обсуждение |
| Ответ на | building pg_dump doesn't work (Alvaro Herrera <alvherre@commandprompt.com>) |
| Ответы |
Re: building pg_dump doesn't work
|
| Список | pgsql-hackers |
Heikki Linnakangas <heikki.linnakangas@enterprisedb.com> writes:
> Perhaps this could be made less ugly by only having the ScanKeywords
> array in the .c file, and #including that into other .c files in
> src/backend/parser, ecpg and pg_dump.
What I'd suggest is something similar to the design of the errcodes.h
header: create a header file containing just the list of PG_KEYWORD
macro calls, and have the different users #include it after defining
that macro appropriately. Having .c files include other .c files is
usually best avoided on least-surprise grounds.
> Not sure what to do about ScanKeywordLookup function.
Yeah, duplicating that function is a bit annoying.
regards, tom lane
В списке pgsql-hackers по дате отправления: