Re: Report error position in partition bound check
От | Ashutosh Bapat |
---|---|
Тема | Re: Report error position in partition bound check |
Дата | |
Msg-id | CAExHW5vXBd39SuU283bCabBsCTHBKbfJ2mxRqiu8JpM2iFFLjg@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Report error position in partition bound check (Alexandra Wang <lewang@pivotal.io>) |
Ответы |
Re: Report error position in partition bound check
Re: Report error position in partition bound check |
Список | pgsql-hackers |
Hi Alexandra, As Michael said it will be considered for the next commitfest. But from a quick glance, a suggestion. Instead of passing NULL parsestate from ATExecAttachPartition, pass make_parsestate(NULL). parse_errorposition() takes care of NULL parse state input, but it might be safer this way. Better if we could cook up a parse state with the query text available in AlterTableUtilityContext available in ATExecCmd(). On Thu, Apr 9, 2020 at 6:36 AM Alexandra Wang <lewang@pivotal.io> wrote: > > Forgot to run make installcheck. Here's the new version of the patch that updated the test answer file. > -- Best Wishes, Ashutosh Bapat
В списке pgsql-hackers по дате отправления: