Re: Virtual generated columns
От | Peter Eisentraut |
---|---|
Тема | Re: Virtual generated columns |
Дата | |
Msg-id | 314146fd-854e-44b8-ac64-0bef2f2d26b0@eisentraut.org обсуждение исходный текст |
Ответ на | Re: Virtual generated columns (vignesh C <vignesh21@gmail.com>) |
Ответы |
Re: Virtual generated columns
|
Список | pgsql-hackers |
On 15.01.25 08:11, vignesh C wrote: > 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? I have a very weak preference for a).
В списке pgsql-hackers по дате отправления: