| From: | Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Should shared_preload_libraries be loaded during binary upgrade? |
| Date: | 2025-05-02 04:44:35 |
| Message-ID: | CAFiTN-tnO7e7T=A==kihSWT9u5YvoiVbvvzikfGdOk3y6Ww+fg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, May 1, 2025 at 7:35 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>
> Bruce Momjian <bruce(at)momjian(dot)us> writes:
> > On Thu, May 1, 2025 at 11:05:56AM +0530, Dilip Kumar wrote:
> >> Does it make sense to load "shared_preload_libraries" during binary
> >> upgrade mode?
>
> > Well, the library might be required to load the data. Why would we
> > avoid it with no known error reports?
>
> You could invent examples that would break things in either direction.
> I'm inclined to leave it alone, because right now the choice is under
> the user's control: she can adjust shared_preload_libraries if needed
> in either the source or target clusters. If we try to force the
> matter, then one set of problem cases is broken without recourse.
Yeah, that makes sense, so let's leave it alone. Thanks.
--
Regards,
Dilip Kumar
EnterpriseDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2025-05-02 04:46:00 | Re: Add an option to skip loading missing publication to avoid logical replication failure |
| Previous Message | Xuneng Zhou | 2025-05-02 04:41:02 | Re: Add an option to skip loading missing publication to avoid logical replication failure |