Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong

Nothing is "changed".  The newly created table never existed and as soon as it did the value of replica identity was default.  It was never anything else.

Sure, maybe we should implement a LIKE option to cover replica identity, but given that it doesn't exist the current behavior is valid - assign what the value would be after a normal create table.  I'd add maybe there should be a way to specify replica identity during create table, not just alter table, but that too is a new feature.

If you don't want the default, PK, replica identity on the new table you are compelled to alter the table after you create it to specify what it should be.  Sure, we don't actually say those words, but since there is nothing in create table that deals with replica identity, that is the conclusion one must draw.  We tend to only document affirmatives - I'm not all that convinced this is going to be an exception.

David J.