Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)

From: Matthias van de Meent <boekewurm+postgres(at)gmail(dot)com>
To: Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com>
Cc: Michael Paquier <michael(at)paquier(dot)xyz>, Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Ignoring BRIN for HOT updates (was: -udpates seems broken)
Date: 2023-03-20 10:24:20
Message-ID: CAEze2Wi9NP0gWNctAGFqOHswLeVdjTvf7gVve0f1yGdHCAuE+g@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Mon, 20 Mar 2023 at 11:11, Tomas Vondra
<tomas(dot)vondra(at)enterprisedb(dot)com> wrote:
>
> On 3/14/23 15:41, Matthias van de Meent wrote:
> > On Tue, 14 Mar 2023 at 14:49, Tomas Vondra
> > <tomas(dot)vondra(at)enterprisedb(dot)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.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Ashutosh Bapat 2023-03-20 10:36:27 Re: server log inflates due to pg_logical_slot_peek_changes/pg_logical_slot_get_changes calls
Previous Message Amit Kapila 2023-03-20 10:14:49 Re: Data is copied twice when specifying both child and parent table in publication