| From: | "kuroda(dot)hayato(at)fujitsu(dot)com" <kuroda(dot)hayato(at)fujitsu(dot)com> |
|---|---|
| To: | "r(dot)takahashi_2(at)fujitsu(dot)com" <r(dot)takahashi_2(at)fujitsu(dot)com> |
| Cc: | Peter Smith <smithpb2250(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, 'Amit Kapila' <amit(dot)kapila16(at)gmail(dot)com>, Bharath Rupireddy <bharath(dot)rupireddyforpostgres(at)gmail(dot)com> |
| Subject: | RE: Multi-Master Logical Replication |
| Date: | 2022-06-14 09:33:27 |
| Message-ID: | TYAPR01MB586652E31FE415FEBAA33AC2F5AA9@TYAPR01MB5866.jpnprd01.prod.outlook.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Dear Takahashi-san,
Thanks for giving feedbacks!
> > I don't know if it requires the kind of code you are thinking but I
> > agree that it is worth considering implementing it as an extension.
>
> I think the other advantage to implement as an extension is that users could
> install the extension to older Postgres.
>
> As mentioned in previous email, the one use case of n-way replication is migration
> from older Postgres to newer Postgres.
>
> If we implement as an extension, users could use n-way replication for migration
> from PG10 to PG16.
>
I think even if LRG is implemented as contrib modules or any extensions,
it will deeply depend on the subscription option "origin" proposed in [1].
So LRG cannot be used for older version, only PG16 or later.
Best Regards,
Hayato Kuroda
FUJITSU LIMITED
| From | Date | Subject | |
|---|---|---|---|
| Next Message | r.takahashi_2@fujitsu.com | 2022-06-14 10:40:51 | RE: Multi-Master Logical Replication |
| Previous Message | Álvaro Herrera | 2022-06-14 09:27:06 | Re: support for MERGE |