Received: from malur.postgresql.org ([2a02:16a8:dc51::56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fJJkL-0008NM-Ev for pgsql-hackers@arkaria.postgresql.org; Thu, 17 May 2018 14:19:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fJJkK-0003hi-9H for pgsql-hackers@arkaria.postgresql.org; Thu, 17 May 2018 14:19:08 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fJJkJ-0003hX-Ob for pgsql-hackers@lists.postgresql.org; Thu, 17 May 2018 14:19:07 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1fJJkG-0001Cn-7P for pgsql-hackers@postgresql.org; Thu, 17 May 2018 14:19:06 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id w4HEIut4027789; Thu, 17 May 2018 10:18:56 -0400 From: Tom Lane To: Robert Haas cc: Arthur Zakirov , Tomas Vondra , Pavel Stehule , Andres Freund , Ildus Kurbangaliev , pgsql-hackers Subject: Re: [PROPOSAL] Shared Ispell dictionaries In-reply-to: References: <20180322105603.GA23544@zakirov.localdomain> <28250.1521924996@sss.pgh.pa.us> <25186.1521951490@sss.pgh.pa.us> <20180325205408.GA19457@arthur.localdomain> <27296.1522078068@sss.pgh.pa.us> <20180327121954.GA12726@zakirov.localdomain> <20180516113631.GA29544@zakirov.localdomain> <20180516204230.GA2397@artur-book.localdomain> Comments: In-reply-to Robert Haas message dated "Thu, 17 May 2018 09:57:59 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <27787.1526566736.1@sss.pgh.pa.us> Date: Thu, 17 May 2018 10:18:56 -0400 Message-ID: <27788.1526566736@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Robert Haas writes: > ... Assuming that we can > convince ourselves that that much is OK, I don't see why using a > syscache callback to help ensure that the mappings are blown away in > an at-least-somewhat-timely fashion is worse than any other approach. I think the point you've not addressed is that "syscache callback occurred" does not equate to "object was dropped". Can the code survive having this occur at any invalidation point? (CLOBBER_CACHE_ALWAYS testing would soon expose any fallacy there.) regards, tom lane