Личный кабинет
Укажите e-mail, на который будет выслан код восстановления пароля.
На указанный вами адрес e-mail был выслан код подтверждения аккаунта. Введите полученный код для продолжения:
Введите новый пароль два раза:
> On 15 November 2016 at 15:03, Aleksander Alekseev <a.alekseev@postgrespro.ru> wrote:> Hello.> > I took a look on the latest -v4 patch. I would like to note that this> patch breaks a backward compatibility. For instance sr_plan extension[1]> stop to compile with errorsThank you for the feedback.Well, if we're speaking about this particular extension, if I understoodcorrectly, it fetches all parse tree nodes from Postgres and generates codeusing this information. So to avoid compilation problems I believe you need torun `make USE_PGXS=1 genparser` again (it worked for me, I don't see anymentions of `ArrayRef`).But speaking generally, I don't see how we can provide backward compatibilityfor those extensions, who are strongly coupled with implementation details ofparsing tree. I mean, in terms of interface it's mostly about to replace`ArrayRef` to `SubscriptingRef`, but I think it's better to do it in theextension code.
В списке pgsql-hackers по дате отправления: