pg.ddx.io  pgsql-hackers@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Euler Taveira <euler@eulerto.com>
Cc: Ajin Cherian <itsajin@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Subject: Re: First draft of the PG 15 release notes
Date: Thu, 12 May 2022 10:22:17 -0400
Message-ID: <Yn0YGa71P7ABzHoH@momjian.us> (raw)
In-Reply-To: <7b1a2c66-e387-40a1-a9ee-419787dbf4a9@www.fastmail.com>
References: <YnqIT8kpiO3m6SD7@momjian.us>
	<CAFPTHDbspst46vp6vtj_p67_AE7W4FL=bdMoY2nSiSRxm0083w@mail.gmail.com>
	<Yn0Tqm5Smlx6ZHxK@momjian.us>
	<7b1a2c66-e387-40a1-a9ee-419787dbf4a9@www.fastmail.com>

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






view thread (145+ messages)  latest in thread

Message-ID: <Yn0YGa71P7ABzHoH@momjian.us>
Permalink:  ../Yn0YGa71P7ABzHoH@momjian.us/
Also on:    postgresql.org/message-id/Yn0YGa71P7ABzHoH@momjian.us

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-hackers@postgresql.org
  Cc: bruce@momjian.us, euler@eulerto.com, itsajin@gmail.com
  Subject: Re: First draft of the PG 15 release notes
  In-Reply-To: <Yn0YGa71P7ABzHoH@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox