Re: Virtual generated columns
От | vignesh C |
---|---|
Тема | Re: Virtual generated columns |
Дата | |
Msg-id | CALDaNm2v-TcAcddXtGOx+CQQ8VnQ3qvkMfEWSRipGj8az0QejQ@mail.gmail.com обсуждение исходный текст |
Ответ на | Virtual generated columns (Peter Eisentraut <peter@eisentraut.org>) |
Ответы |
Re: Virtual generated columns
|
Список | pgsql-hackers |
On Tue, 14 Jan 2025 at 19:08, Peter Eisentraut <peter@eisentraut.org> wrote: > > > I've also added a patch that addresses logical replication. It > basically adds back some of the prohibitions against including generated > columns in publications that have been lifted, but this time only for > virtual generated columns, and amends the documentation. It doesn't > rename the publication option "publish_generated_columns", but maybe > that should be done. There are two potential approaches we could take to address the "publish_generated_columns" option: a) We could support multiple values for publish_generated_columns, such as 'none', 'stored', and 'virtual', as Amit suggested in [1]. b) Alternatively, we could rename publish_generated_columns to publish_stored_generated_columns. Both options seem reasonable to me. Do you have a preference for which approach would be better? [1] - https://www.postgresql.org/message-id/CAA4eK1JfEZUdtC5896vwEZFXBZnQ4aTDDXQxv3NOaosYu973Pw@mail.gmail.com Regards, Vignesh
В списке pgsql-hackers по дате отправления: