[COMMITTERS] pgsql: Fix portability issue in isolationtester grammar.

2015-05-27 Thread Tom Lane
Fix portability issue in isolationtester grammar. specparse.y and specscanner.l used "string" as a token name. Now, bison likes to define each token name as a macro for the token code it assigns, which means those names are basically off-limits for any other use within the grammar file or include

[COMMITTERS] pgsql: Fix portability issue in isolationtester grammar.

2015-05-27 Thread Tom Lane
Fix portability issue in isolationtester grammar. specparse.y and specscanner.l used "string" as a token name. Now, bison likes to define each token name as a macro for the token code it assigns, which means those names are basically off-limits for any other use within the grammar file or include

[COMMITTERS] pgsql: Fix portability issue in isolationtester grammar.

2015-05-27 Thread Tom Lane
Fix portability issue in isolationtester grammar. specparse.y and specscanner.l used "string" as a token name. Now, bison likes to define each token name as a macro for the token code it assigns, which means those names are basically off-limits for any other use within the grammar file or include

[COMMITTERS] pgsql: Fix portability issue in isolationtester grammar.

2015-05-27 Thread Tom Lane
Fix portability issue in isolationtester grammar. specparse.y and specscanner.l used "string" as a token name. Now, bison likes to define each token name as a macro for the token code it assigns, which means those names are basically off-limits for any other use within the grammar file or include

[COMMITTERS] pgsql: Fix portability issue in isolationtester grammar.

2015-05-27 Thread Tom Lane
Fix portability issue in isolationtester grammar. specparse.y and specscanner.l used "string" as a token name. Now, bison likes to define each token name as a macro for the token code it assigns, which means those names are basically off-limits for any other use within the grammar file or include