Re: pgsql: Avoid invalidating all RelationSyncCache entries on publication

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
Cc: Amit Kapila <akapila(at)postgresql(dot)org>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: pgsql: Avoid invalidating all RelationSyncCache entries on publication
Date: 2025-03-18 13:42:38
Message-ID: CA+TgmoaNw1v+pqJiAPV+Esv6KrweRKXERMZNsRk-xOVJrJVEAg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

On Tue, Mar 18, 2025 at 2:30 AM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> I think I should have mentioned the future use and other improvements
> of this work in the commit message.

OK, thanks for the background. Yes, it would have been helpful to
mention at least in general terms that it would unblock other
optimization work.

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-committers by date

  From Date Subject
Next Message Daniel Gustafsson 2025-03-18 14:32:53 pgsql: Add X25519 to the default set of curves
Previous Message Robert Haas 2025-03-18 13:30:24 pgsql: Add some new hooks so extensions can add details to EXPLAIN.

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrei Lepikhov 2025-03-18 13:58:12 Re: making EXPLAIN extensible
Previous Message Robert Haas 2025-03-18 13:40:52 Re: optimize file transfer in pg_upgrade