| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Allow streaming the changes after speculative aborts. |
| Date: | 2021-06-29 07:27:06 |
| Message-ID: | CAFiTN-vZrEq3_zdWXcGF+0cqnM=vNBKVf0NyFw_+ZEg0wXXOxA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Fri, Jun 25, 2021 at 12:24 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
>
> Till now, we didn't allow to stream the changes in logical replication
> till we receive speculative confirm or the next DML change record
> after speculative inserts. The reason was that we never use to process
> speculative aborts but after commit 4daa140a2f it is possible to
> process them so we can allow streaming once we receive speculative
> abort after speculative insertion. See attached.
>
> I think this is a minor improvement in the logical replication of
> in-progress transactions. I have verified this for speculative aborts
> and it allows streaming once we receive the spec_abort change record.
Yeah, this improvement makes sense. And the patch looks fine to me.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Magnus Hagander | 2021-06-29 07:28:04 | Re: [Patch] change the default value of shared_buffers in postgresql.conf.sample |
| Previous Message | Michael Paquier | 2021-06-29 06:59:34 | Re: Speed up pg_checksums in cases where checksum already set |