Re: Add pg_get_publication_ddl function

Поиск
Список
Период
Сортировка
Искать
От
Jonathan Gonzalez V.
Тема
Re: Add pg_get_publication_ddl function
Дата
в 14:35:33
Msg-id
87wlw83q0q.fsf@gmail.com
Список
Дерево обсуждения
Add pg_get_publication_ddl function "Jonathan Gonzalez V." <jonathan.abdiel@gmail.com>
Re: Add pg_get_publication_ddl function Hüseyin Demir <huseyin.d3r@gmail.com>
Re: Add pg_get_publication_ddl function Peter Smith <smithpb2250@gmail.com>
Re: Add pg_get_publication_ddl function Cary Huang <cary.huang@highgo.ca>
Re:Add pg_get_publication_ddl function "zengman" <zengman@halodbtech.com>
solai v  writes:

Hello,

>
> [...] One thing I noticed is that the function currently returns
> SETOF text, producing multiple DDL statements such as CREATE
> PUBLICATION followed by ALTER PUBLICATION ... OWNER TO .... I wanted
> to check whether this is the intended long-term API design, as most
> existing pg_get_* functions return a single text value.

Yes this is by design, it's documented that they will return the
OWNER[1] unless that publications doesn't intend to have an OWNER in the
DDL.

> I also noticed
> that publication options are emitted as quoted values, for example:
>
> publish='insert, update'
> publish_generated_columns='none'
> publish_via_partition_root='false'
>
> Would it make sense to emit enum-like and boolean values in their
> native SQL form instead, such as:
>
> publish = 'insert, update'
> publish_generated_columns = none
> publish_via_partition_root = false

Yes, this was already handled by Peter Smith[1] email

Regards!

[1] https://www.postgresql.org/docs/19/functions-info.html#FUNCTIONS-GET-OBJECT-DDL 
[2] https://www.postgresql.org/message-id/CAHut%2BPvyd3vN_LV8ppyX6Vu7pKdBhC5M3_zHN7gdJCvz1%3DkKHQ%40mail.gmail.com 

--
Jonathan Gonzalez V.
EDB
https://www.enterprisedb.com


В списке pgsql-hackers по дате отправления
От: Shlok Kyal
Дата:
От: Rafia Sabih
Дата:
FAQ