Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
От | dbman@sqlexec.com |
---|---|
Тема | Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong |
Дата | |
Msg-id | fade757a-328a-46fc-a117-8d22459e35d7@sqlexec.com обсуждение исходный текст |
Ответ на | Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong ("David G. Johnston" <david.g.johnston@gmail.com>) |
Ответы |
Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
|
Список | pgsql-bugs |
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@postgresql.org> wrote:The following bug has been logged on the website:
Bug reference: 19013
Logged by: Michael Vitale
Email address: dbman@sqlexec.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?
В списке pgsql-bugs по дате отправления: