Re: Added schema level support for publication.
От | Amit Kapila |
---|---|
Тема | Re: Added schema level support for publication. |
Дата | |
Msg-id | CAA4eK1+=FRnrZZDa1VMjkn2Dpw011=Q8djdSMkiBSOS9s2J0uw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: Added schema level support for publication. (Amit Kapila <amit.kapila16@gmail.com>) |
Список | pgsql-hackers |
On Mon, Sep 13, 2021 at 5:11 PM Amit Kapila <amit.kapila16@gmail.com> wrote: > > On Sun, Sep 12, 2021 at 8:43 PM vignesh C <vignesh21@gmail.com> wrote: > > > > Thanks for the changes, the suggested changes make the parsing code > > simpler. I have merged the changes to the main patch. Attached v27 > > patch has the changes for the same. > > > > +pubobj_name: ColId { $$ = list_make1(makeString($1)); } > + | ColId indirection { $$ = lcons(makeString($1), $2); } > ; > > I think "ColId indirection" should handle catalog and schema name as > we are doing in qualified_name. See attached (this can be applied atop > v27-0002). The one other improvement we can do here is to extract the > common code from qualified_name (especially for "ColId indirection") > and pubobj_name. What do you think? > One more suggestion for changes in gram.y: @@ -12430,7 +12476,14 @@ relation_expr: $$->inh = true; $$->alias = NULL; } - | qualified_name '*' + | special_relation_expr + { + $$ = $1; + } + ; + +special_relation_expr: + qualified_name '*' I am not sure if naming the above rule as special_relation_expr is a good idea. Can we name it as extended_relation_expr? -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: