Re: Unhappy about API changes in the no-fsm-for-small-rels patch

From: Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>
To: John Naylor <john(dot)naylor(at)2ndquadrant(dot)com>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Unhappy about API changes in the no-fsm-for-small-rels patch
Date: 2019-05-03 08:44:53
Message-ID: CAA4eK1L1pHDpcvYwbw7WveR14ea5RkRAmxXikpX-fGAQxEHN9w@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, May 3, 2019 at 11:43 AM John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> wrote:
> On Thu, May 2, 2019 at 4:57 PM Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> wrote:
> > On Thu, May 2, 2019 at 12:39 PM John Naylor <john(dot)naylor(at)2ndquadrant(dot)com> wrote:
> > >
> > Can you please test/review?
>
> There isn't enough time. But since I already wrote some debugging
> calls earlier (attached), I gave it a brief spin, I found this patch
> isn't as careful as HEAD making sure we don't try the same block twice
> in a row. If you insert enough tuples into an empty table such that we
> need to extend, you get something like this:
>
> DEBUG: Not enough space on block 0
> DEBUG: Now trying block 0
> DEBUG: Not enough space on block 0
> DEBUG: Updating local map for block 0
>
> At this point, I'm sorry to say, but I'm in favor of reverting.
>

Fair enough. I think we have tried to come up with a patch for an
alternative approach, but it needs time. I will revert this tomorrow.

--
With Regards,
Amit Kapila.
EnterpriseDB: http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Rajkumar Raghuwanshi 2019-05-03 09:26:04 Statistical aggregate functions are not working with partitionwise aggregate
Previous Message Peter Eisentraut 2019-05-03 07:53:13 Re: pg_upgrade --clone error checking