| From: | Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> |
|---|---|
| To: | "Hayato Kuroda (Fujitsu)" <kuroda(dot)hayato(at)fujitsu(dot)com> |
| Cc: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, Michael Paquier <michael(at)paquier(dot)xyz>, "pgsql-hackers(at)lists(dot)postgresql(dot)org" <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Грем Снорт <grem(dot)snoort(at)gmail(dot)com> |
| Subject: | Re: [PATCH TEST] Fix logical replication setup in subscription test `t/009_matviews.pl` |
| Date: | 2025-10-13 11:48:32 |
| Message-ID: | CAA4eK1L_pDLpnguYpqqTF8obKKzHPFvqVHhgrVQvd5xM1djAnA@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Oct 12, 2025 at 11:29 AM Hayato Kuroda (Fujitsu)
<kuroda(dot)hayato(at)fujitsu(dot)com> wrote:
>
> Dear Amit, Ashutosh,
>
> > Thanks for the analysis. I think we should go with the simple patch
> > proposed in this thread to improve this test and that too only for
> > HEAD.
>
> To confirm, are you suggesting something like attached? It initially creates MVs
> on both instances, then ensure REFRESH MATERIALIZED VIEW won't be replicated.
> It also fixed the issue reported by Грем.
>
What difference REFRESH will make instead of CREATE? I think it is
okay to just patch what is posted by the reporter in the first email
[1] in this thread.
--
With Regards,
Amit Kapila.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | David G. Johnston | 2025-10-13 11:55:36 | Re: Improve docs for n_distinct_inherited |
| Previous Message | Xuneng Zhou | 2025-10-13 11:41:06 | Re: pgstattuple: Use streaming read API in pgstatindex functions |