On Sat, Sep 21, 2024 at 3:19 AM Masahiko Sawada <sawada.m...@gmail.com> wrote: > > On Thu, Sep 19, 2024 at 9:26 PM Amit Kapila <amit.kapil...@gmail.com> wrote: > > > > > > > > OK. Let me give some examples below to help understand this idea. > > > > > > Please correct me if these are incorrect. > > > > > > Examples, when publish_generated_columns=true: > > > > > > CREATE PUBLICATION pub1 FOR t1(a,b,gen2), t2 WITH > > > (publish_generated_columns=true) > > > t1 -> publishes a, b, gen2 (e.g. what column list says) > > > t2 -> publishes c, d + ALSO gen1, gen2 > > > > > > CREATE PUBLICATION pub1 FOR t1, t2(gen1) WITH > > > (publish_generated_columns=true) > > > t1 -> publishes a, b + ALSO gen1, gen2 > > > t2 -> publishes gen1 (e.g. what column list says) > > > > > > > These two could be controversial because one could expect that if > > "publish_generated_columns=true" then publish generated columns > > irrespective of whether they are mentioned in column_list. I am of the > > opinion that column_list should take priority the results should be as > > mentioned by you but let us see if anyone thinks otherwise. > > I agree with Amit. We also publish t2's future generated column in the > first example and t1's future generated columns in the second example. >
Right, it would be good to have at least one test that shows future generated columns also get published wherever applicable (like where column_list is not given and publish_generated_columns is true). -- With Regards, Amit Kapila.
