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

On Wednesday, August 6, 2025, dbman(at)sqlexec(dot)com <dbman(at)sqlexec(dot)com> wrote:

> On 8/5/2025 7:01 PM, David G. Johnston wrote:
>
> On Tue, Aug 5, 2025 at 2:43 PM PG Bug reporting form <
> noreply(at)postgresql(dot)org> wrote:
>
>> The following bug has been logged on the website:
>>
>> Bug reference: 19013
>> Logged by: Michael Vitale
>> Email address: dbman(at)sqlexec(dot)com
>> PostgreSQL version: 17.5
>> Operating system: CentOS 8 Streams
>> Description:
>>
>>
> We don't document that the replica identity attribute of a table is
> something that can be copied. 'ALL' only covers those things which are
> documented as being copy-able.
>
> David J.
>
> I understand your logic about not everything is copy-able, just what is
> documented, but this is a different case. I am not complaining that it is
> not copying the REPLICA IDENTITY, but rather that it is copying it in a
> WRONG WAY, changing its property from FULL to DEFAULT. I think that is a
> reasonable complaint. If you are going to attempt to copy it erroneously,
> then I think you should consider that a bug and fix it. Otherwise, remove
> it and don't try to copy it. Does that seem reasonable?
>

Reading the docs, if you just perform a create table (no like) you’ll find
pg_class.relreplident is set to “d”. That field is never null. There is
no concept of “remove it”.

David J.