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

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

On April 18, 2019 7:53:58 PM PDT, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>Amit Kapila <amit(dot)kapila16(at)gmail(dot)com> writes:
>> I am thinking that we should at least give it a try to move the map
>to
>> rel cache level to see how easy or difficult it is and also let's
>wait
>> for a day or two to see if Andres/Tom has to say anything about this
>> or on the response by me above to improve the current patch.
>
>FWIW, it's hard for me to see how moving the map to the relcache isn't
>the right thing to do. You will lose state during a relcache flush,
>but that's still miles better than how often the state gets lost now.

+1
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2019-04-19 05:55:53 Re: bug in update tuple routing with foreign partitions
Previous Message Etsuro Fujita 2019-04-19 05:40:20 Re: bug in update tuple routing with foreign partitions