Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
От | Peter Geoghegan |
---|---|
Тема | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} |
Дата | |
Msg-id | CAM3SWZR1OcoOK6HgPpXEm2hpJPvjf6o-9cUOoovMQ7c7wzU-UA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: INSERT ... ON CONFLICT {UPDATE | IGNORE} (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
Re: INSERT ... ON CONFLICT {UPDATE | IGNORE}
|
Список | pgsql-hackers |
On Mon, Dec 15, 2014 at 4:33 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Jeff Janes <jeff.janes@gmail.com> writes: >> It seems like IGNORE is getting replaced by the preprocessor with something >> else, but I don't know how to get my hands on the intermediate file after >> the preprocessor has done its thing. > > Maybe IGNORE is defined as a macro in MinGW? > Try s/IGNORE/IGNORE_P/g throughout the patch. BTW, the gcc -E flag does this. So figure out what exact arguments MinGW's gcc is passed in the ordinary course of compiling gram.c, and prepend "-E" to the list of existing flags while manually executing gcc -- that should let you know exactly what's happening here. -- Peter Geoghegan
В списке pgsql-hackers по дате отправления: