Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knIB7-0004pj-3v for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Dec 2020 09:24:01 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1knIB6-0005NE-2i for pgsql-bugs@arkaria.postgresql.org; Thu, 10 Dec 2020 09:24:00 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knIB5-0005N5-Nv for pgsql-bugs@lists.postgresql.org; Thu, 10 Dec 2020 09:23:59 +0000 Received: from forward501j.mail.yandex.net ([2a02:6b8:0:801:2::111]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1knIB1-0003Q3-7v for pgsql-bugs@lists.postgresql.org; Thu, 10 Dec 2020 09:23:58 +0000 Received: from mxback4q.mail.yandex.net (mxback4q.mail.yandex.net [IPv6:2a02:6b8:c0e:6d:0:640:ed15:d2bd]) by forward501j.mail.yandex.net (Yandex) with ESMTP id 2B8F533808C4; Thu, 10 Dec 2020 12:23:51 +0300 (MSK) Received: from localhost (localhost [::1]) by mxback4q.mail.yandex.net (mxback/Yandex) with ESMTP id 0IS4rHigIl-NotKgooC; Thu, 10 Dec 2020 12:23:50 +0300 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zsrv.org; s=mail; t=1607592230; bh=eehE3PIm3GVplPBL5OppbokTyKwb7nMrRpa9S+902UY=; h=References:Date:Message-Id:Subject:In-Reply-To:To:From; b=dKSIB0MyO3wh06VitumHqiH5n++w3V20JtmiO0tQZyfCpM872u9kPb+N/VsDi1Xnv brrolGXQyT+B/8Ugp1/rCrCKHlj0QsjniafffwB3hqmYNpyJTsYwdp68eG+kSXsl/K Xz75uDs1bzyR04qGe27rNbTJHoaPSufe/zPYUPZw= Authentication-Results: mxback4q.mail.yandex.net; dkim=pass header.i=@zsrv.org Received: by vla5-b23e4d8cdbda.qloud-c.yandex.net with HTTP; Thu, 10 Dec 2020 12:23:50 +0300 From: Sergei Kornilov To: "leiyanliang@highgo.com" , "pgsql-bugs@lists.postgresql.org" In-Reply-To: <16770-752d7e16b4ebb3b2@postgresql.org> References: <16770-752d7e16b4ebb3b2@postgresql.org> Subject: Re: BUG #16770: PostgreSQL software V11 does not eliminate this recheck_on_update option? MIME-Version: 1.0 X-Mailer: Yamail [ http://yandex.ru ] 5.0 Date: Thu, 10 Dec 2020 12:23:50 +0300 Message-Id: <126181607591827@mail.yandex.ru> Content-Transfer-Encoding: 7bit Content-Type: text/plain List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello It's related to commits: https://git.postgresql.org/pg/commitdiff/c203d6cf81b4d7e43edb2b75ec1b741ba48e04e0 https://git.postgresql.org/pg/commitdiff/5d28c9bd73e29890cccd3f6b188b86f81031f671 https://git.postgresql.org/pg/commitdiff/1c53c4dec3985512f7f2f53c9d76a5295cd0a2dd Feature was reverted in master. Remains present in pg11, but nonfunctional and undocumented to avoid an ABI break for code touching relcache entries. regards, Sergei