| From: | Euler Taveira <euler(dot)taveira(at)2ndquadrant(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | Dilip Kumar <dilipbalaut(at)gmail(dot)com>, Euler Taveira <euler(at)timbira(dot)com(dot)br>, Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: logical replication empty transactions |
| Date: | 2020-03-04 01:47:22 |
| Message-ID: | CAH503wBXk18nWUQYbAeLuJY1jSsEiLUyF5+ubi2v4AaAjbvCHg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, 3 Mar 2020 at 05:24, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> Another idea could be that we stream the transaction after some
> threshold number (say 100 or anything we think is reasonable) of empty
> xacts. This will reduce the traffic without tinkering with the core
> design too much.
>
>
> Amit, I suggest an interval to control this setting. Time is something we
have control; transactions aren't (depending on workload).
pg_stat_replication query interval usually is not milliseconds, however,
you can execute thousands of transactions in a second. If we agree on that
idea I can add it to the patch.
Regards,
--
Euler Taveira http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Peter Geoghegan | 2020-03-04 01:58:24 | Re: [PATCH] kNN for btree |
| Previous Message | Kyotaro Horiguchi | 2020-03-04 00:12:18 | Re: Back-patching -Wno-format-truncation. |