Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
От | David G. Johnston |
---|---|
Тема | Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong |
Дата | |
Msg-id | CAKFQuwbnfSySRV-axfQXAsd37ERQf=8L5FQSVnRM27aBmW5uFA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong ("dbman@sqlexec.com" <dbman@sqlexec.com>) |
Ответы |
Re: BUG #19013: When creating a table with the "...LIKE...INCLUDING ALL" construct, REPLICA IDENTITY output is wrong
|
Список | pgsql-bugs |
On Wednesday, August 6, 2025, dbman@sqlexec.com <dbman@sqlexec.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@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?
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.
В списке pgsql-bugs по дате отправления: