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

From: "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com>
To: dbman(at)sqlexec(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org
Subject: Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
Date: 2025-08-05 23:01:18
Message-ID: CAKFQuwba_gRmzi4C9Uu=_+AW8L-z=V0MpkPgk3HNBoKkfA09zA@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

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.

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Alexandra Wang 2025-08-05 23:30:12 Re: BUG #16961: Could not access status of transaction
Previous Message PG Bug reporting form 2025-08-05 21:26:56 BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong