Re: Ignoring BRIN for HOT updates (was: -udpates seems broken) - Mailing list pgsql-hackers

From Matthias van de Meent
Subject Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)
Date
Msg-id CAEze2Wi9NP0gWNctAGFqOHswLeVdjTvf7gVve0f1yGdHCAuE+g@mail.gmail.com
Whole thread Raw
In response to Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)  (Tomas Vondra <tomas.vondra@enterprisedb.com>)
Responses Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)
List pgsql-hackers
On Mon, 20 Mar 2023 at 11:11, Tomas Vondra
<tomas.vondra@enterprisedb.com> wrote:
>
> On 3/14/23 15:41, Matthias van de Meent wrote:
> > On Tue, 14 Mar 2023 at 14:49, Tomas Vondra
> > <tomas.vondra@enterprisedb.com> wrote:
> >>
> >>> ...
> >
> >> If you agree with these changes, I'll get it committed.
> >
> > Yes, thanks!
> >
>
> I've tweaked the patch per the last round of comments, cleaned up the
> commit message a bit (it still talked about unused bit in tuple header
> and so on), and pushed it.
>
> Thanks for fixing the issues that got the patch reverted last year!

Thanks for helping getting this in!


Kind regards,

Matthias van de Meent.



pgsql-hackers by date:

Previous
From: Amit Kapila
Date:
Subject: Re: Data is copied twice when specifying both child and parent table in publication
Next
From: Ashutosh Bapat
Date:
Subject: Re: server log inflates due to pg_logical_slot_peek_changes/pg_logical_slot_get_changes calls