Re: First draft of the PG 15 release notes
От | vignesh C |
---|---|
Тема | Re: First draft of the PG 15 release notes |
Дата | |
Msg-id | CALDaNm1ydPKs1QWKv+bOwRtkrCeU=0t-BN9P_YkO2RgLzry_rA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: First draft of the PG 15 release notes (Bruce Momjian <bruce@momjian.us>) |
Ответы |
Re: First draft of the PG 15 release notes
|
Список | pgsql-hackers |
I wonder if this is worth mentioning: Raise a WARNING for missing publications. commit 8f2e2bbf145384784bad07a96d461c6bbd91f597 https://git.postgresql.org/gitweb/?p=postgresql.git;a=commitdiff;h=8f2e2bbf145384784bad07a96d461c6bbd91f597 Regards, Vignesh On Thu, May 12, 2022 at 7:52 PM Bruce Momjian <bruce@momjian.us> wrote: > > On Thu, May 12, 2022 at 11:12:54AM -0300, Euler Taveira wrote: > OB> On Thu, May 12, 2022, at 11:03 AM, Bruce Momjian wrote: > > > > I looked at that but thought that everyone would already assume we > > skipped replication of empty transactions, and I didn't see much impact > > for the user, so I didn't include it. > > > > It certainly has an impact on heavy workloads that replicate tables with few > > modifications. It receives a high traffic of 'begin' and 'commit' messages that > > the previous Postgres versions have to handle (discard). I would classify it as > > a performance improvement for logical replication. Don't have a strong opinion > > if it should be mentioned or not. > > Oh, so your point is that a transaction that only has SELECT would > previously send an empty transaction? I thought this was only for apps > that create literal empty transactions, which seem rare. > > -- > Bruce Momjian <bruce@momjian.us> https://momjian.us > EDB https://enterprisedb.com > > Indecision is a decision. Inaction is an action. Mark Batterson > > >
В списке pgsql-hackers по дате отправления: