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 1fqegx-0004f3-ST for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Aug 2018 13:21:28 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1fqegw-0006Or-Bz for pgsql-hackers@arkaria.postgresql.org; Fri, 17 Aug 2018 13:21:26 +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 1fqegw-0006Ok-1Z for pgsql-hackers@lists.postgresql.org; Fri, 17 Aug 2018 13:21:26 +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 1fqegs-00063p-NB for pgsql-hackers@lists.postgresql.org; Fri, 17 Aug 2018 13:21:24 +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 w7HDLGXl012981; Fri, 17 Aug 2018 09:21:16 -0400 From: Tom Lane To: Dave Cramer cc: Jonathan Katz , Michael Paquier , dian.m.fay@gmail.com, PostgreSQL Hackers Subject: Re: docs: note ownership requirement for refreshing materialized views In-reply-to: References: <745abbd2-a1a0-ead8-2cb2-768c16747d97@gmail.com> <55498B5B-0155-4B0E-9B97-23167F8CB380@excoventures.com> <20180816011534.GK3681@paquier.xyz> <862321D6-495D-4A62-94D2-17D6EDF87A41@excoventures.com> Comments: In-reply-to Dave Cramer message dated "Fri, 17 Aug 2018 09:08:23 -0400" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <12979.1534512076.1@sss.pgh.pa.us> Date: Fri, 17 Aug 2018 09:21:16 -0400 Message-ID: <12980.1534512076@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Dave Cramer writes: > So it seems this patch is being ignored in this thread. Well, Jonathan did kind of hijack what appears to be a thread about documentation (with an already-committed fix). I'd suggest reposting that patch in its own thread and adding it to the next CF. regards, tom lane