Heikki Linnakangas wrote:
> Alvaro Herrera wrote:
>> /*
>> + * We don't want to include the gram.h file on frontend builds, except
>> ECPG, so
>> + * leave out the second struct member in that case.
>> + */
>> + #if !defined FRONTEND || defined ECPG_COMPILE
>> + #define PG_KEYWORD(a,b,c) {a,b,c}
>> + #else
>> + #define PG_KEYWORD(a,b,c) {a,c}
>> + #endif
>
> Doesn't that put 'c' into the wrong field in ScanKeyword struct? It only
> compiles because both 'value' and 'category' are int16.
No, because I had the header with the second field omitted too.
--
Alvaro Herrera http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
