| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Euler Taveira <euler(at)eulerto(dot)com> |
| Cc: | Ajin Cherian <itsajin(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: First draft of the PG 15 release notes |
| Date: | 2022-05-12 14:22:17 |
| Message-ID: | Yn0YGa71P7ABzHoH@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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(at)momjian(dot)us> https://momjian.us
EDB https://enterprisedb.com
Indecision is a decision. Inaction is an action. Mark Batterson
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2022-05-12 14:25:03 | Re: gitmaster access |
| Previous Message | Euler Taveira | 2022-05-12 14:12:54 | Re: First draft of the PG 15 release notes |