Re: Dropped and generated columns might cause wrong data on subs when REPLICA IDENTITY FULL

Поиск
Список
Период
Сортировка
От Önder Kalacı
Тема Re: Dropped and generated columns might cause wrong data on subs when REPLICA IDENTITY FULL
Дата
Msg-id CACawEhVTFnDh70eJGh_ww1nYu1SvMSqyECxLQVxjcWzf4ybDEA@mail.gmail.com
обсуждение исходный текст
Ответ на RE: Dropped and generated columns might cause wrong data on subs when REPLICA IDENTITY FULL  ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>)
Ответы RE: Dropped and generated columns might cause wrong data on subs when REPLICA IDENTITY FULL  ("shiy.fnst@fujitsu.com" <shiy.fnst@fujitsu.com>)
Список pgsql-hackers
Hi Shi Yu,



Is there any reasons why we drop column here? Dropped column case has been
tested on table dropped_cols. The generated column problem can be detected
without dropping columns on my machine.

We don't really need to, if you check the first patch, we don't have DROP for generated case. I mostly
wanted to make the test a little more interesting, but it also seems to be a little confusing.

Now attaching v2 where we do not drop the columns. I don't have strong preference on
which patch to proceed with, mostly wanted to attach this version to progress faster (in case
you/Amit considers this one better).

Thanks,
Onder
 
Вложения

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Michael Paquier
Дата:
Сообщение: Re: User functions for building SCRAM secrets
Следующее
От: Peter Eisentraut
Дата:
Сообщение: meson: Fix support for empty darwin sysroot