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

dbman@sqlexec.com <dbman@sqlexec.com>

From: "dbman@sqlexec.com" <dbman@sqlexec.com>

To: Kirill Reshke <reshkekirill@gmail.com>

Cc: "David G. Johnston" <david.g.johnston@gmail.com>, "pgsql-bugs@lists.postgresql.org" <pgsql-bugs@lists.postgresql.org>

Date: 2025-08-06T16:52:28Z

Lists: pgsql-bugs

Commits

Same data as JSON: GET /api/v1/messages/:b64id/commits the thread's linked commits as JSON, with link sources. API reference →

Add the notion of REPLICA IDENTITY for a table.
- 07cacba983ef 9.4.0 cited

On 8/6/2025 12:32 PM, Kirill Reshke wrote:
> It's hard (to me, at least) to say what is `intended` DDL here.

Why is it hard?  If the pg_dump output or /d schema.tablename output 
indicates a REPLICA IDENTITY of either FULL or INDEX, then it seems it 
should be obvious that the CREATE TABLE ... LIKE output should be 
similar, but instead it will show REPLICA IDENTITY DEFAULT.

Regards,

Michael V