Re: Added schema level support for publication.
От | Amit Kapila |
---|---|
Тема | Re: Added schema level support for publication. |
Дата | |
Msg-id | CAA4eK1+vKa6e4gowSdtsmweKFc9zqjF_jCyqUwZoPqYG7h0uaw@mail.gmail.com обсуждение исходный текст |
Ответ на | RE: Added schema level support for publication. ("houzj.fnst@fujitsu.com" <houzj.fnst@fujitsu.com>) |
Ответы |
RE: Added schema level support for publication.
|
Список | pgsql-hackers |
On Fri, Sep 10, 2021 at 8:54 AM houzj.fnst@fujitsu.com <houzj.fnst@fujitsu.com> wrote: > > From Friday, September 10, 2021 10:33 AM Hou Zhijie<houzj.fnst@fujitsu.com> wrote: > > Besides, If we don't want to use a new flag to distinguish tablename and schemaname, > We can only check the NodeTag to distinguish the difference. > > Attach two diff patches based on the latest schema patch > which change the code with a flag and without a flag. > I would prefer a version without additional flags unless you think it is difficult to extend it in the future for other objects like sequences which as far as I can see shouldn't be the case. Is there a reason to define pubobj_name similar to any_name? If so, then please do add the comments. One reason I could think of is that any_name is not used for schema names currently which might have motivated you to define a separate naming convention for publication. -- With Regards, Amit Kapila.
В списке pgsql-hackers по дате отправления: