Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iu4oG-0002FV-EW for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jan 2020 01:27:56 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iu4oF-0006aN-0f for pgsql-hackers@arkaria.postgresql.org; Wed, 22 Jan 2020 01:27:55 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iu4oE-0006aG-K4 for pgsql-hackers@lists.postgresql.org; Wed, 22 Jan 2020 01:27:54 +0000 Received: from mail-yw1-xc35.google.com ([2607:f8b0:4864:20::c35]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iu4oB-0002lu-40 for pgsql-hackers@lists.postgresql.org; Wed, 22 Jan 2020 01:27:53 +0000 Received: by mail-yw1-xc35.google.com with SMTP id 10so2461712ywv.5 for ; Tue, 21 Jan 2020 17:27:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mime-version:content-disposition :user-agent; bh=52T8OrnN8ijTXXuXR9MiRxT50Cw5yGpnSStmw97KpFc=; b=ZZC076yKU4LdXbtZcobk1KTnOtCOSg5r7nNIvNBldNf174MZPKYZVhUGpe9UeghEWy V4HytrWGXWNofDft/lQdirRPFaYHEHq3pEWF8SOCMS+y0p1Nse3oj33Pv2EI0eRuBNIc +aK7kdPYuQ8UARDb22FtZeLTbDzL0uGXOuAw+wjquU3vdmvo2R/sJzCCEn4LW9XauIyj T1cB5NQ4zzwVj10gscAcwvDN/FAM/arM3JrxdE5rMT4ZLjR34RSUkblycNctywgo0YTW iFiJlwSsIeujokyq1ChGgAWIszX+QnF5G2kCETeboAfx7V3PshRQHjPXp3lDPuModr60 4Dmw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:mime-version :content-disposition:user-agent; bh=52T8OrnN8ijTXXuXR9MiRxT50Cw5yGpnSStmw97KpFc=; b=CjRMqUSba9oQwI2q1r5SoFK3r5OTIWFyHtYus/YsYSoSPcEY0bgmMBSNK2DCl1HjBO +PJocB6ACl4aX7e+n4TtosZKpxPpFPu8YqAfqDSQsbdPMQZKB5nKDKMFGqWRd/nIA56O SuKLPABzWhoX+Eum5CrhWFSfFwM0mH00g4ID0tm4moJJ2WF7X3WD+4vmpfCZHoMdtE7S YaSY3W+YUbS6n4i2lfh3W2YXmY6XSjttCMA3cxmDocf1IV0bH/uDFHL/6Sm2/mD7tYRi hXasJWjM44r5j4J+kJRti7xTaFp9Xt5bIz+B46aY0qZG70qPQHpHmzBufyOgybEnLVMZ Lh4A== X-Gm-Message-State: APjAAAXG77qLtMkwg57XXdG8RT0L+HzXWWLmwkUvwi93yS3n2m04Ke6W jFNYLpNE2JiiXVGBbGjdt+s1aQ== X-Google-Smtp-Source: APXvYqx625l58xMguYEthHRZFHl73gFl1ZKkP9mKDBnoKJDgFG+YckZTpNqaBvPv27MVJbyHHFHQSg== X-Received: by 2002:a81:8686:: with SMTP id w128mr5525597ywf.15.1579656470340; Tue, 21 Jan 2020 17:27:50 -0800 (PST) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id s31sm18507237ywa.30.2020.01.21.17.27.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Jan 2020 17:27:49 -0800 (PST) Received: by pryzbyj (Postfix, from userid 1000) id 0E3B4800831; Tue, 21 Jan 2020 19:27:48 -0600 (CST) Date: Tue, 21 Jan 2020 19:27:47 -0600 From: Justin Pryzby To: Simon Riggs Cc: PostgreSQL Hackers Subject: Re: doc: alter table references bogus table-specific planner parameters Message-ID: <20200122012747.GJ26045@telsasoft.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="5mjPmdht4ZehXHR2" Content-Disposition: inline User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --5mjPmdht4ZehXHR2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Mon, Jan 06, 2020 at 04:33:46AM +0000, Simon Riggs wrote: > On Mon, 6 Jan 2020 at 04:13, Justin Pryzby wrote: > > > I agree with the sentiment of the third doc change, but your patch removes > > > the mention of n_distinct, which isn't appropriate. > > > > I think it's correct to remove n_distinct there, as it's documented previously, > > since e5550d5f. That's a per-attribute option (not storage) and can't be > > specified there. > > OK, then agreed. Attached minimal patch with just this hunk. https://commitfest.postgresql.org/27/2417/ => RFC Justin (I'm resending in a new thread since it looks like the first message was somehow sent as a reply to an unrelated thread.) --5mjPmdht4ZehXHR2 Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="v2-0001-doc-alter-table-references-bogus-table-specific-p.patch" From 23873bbf32740b0f78f2102eb615e6a6aa615b8c Mon Sep 17 00:00:00 2001 From: Justin Pryzby Date: Sun, 5 Jan 2020 19:39:29 -0600 Subject: [PATCH v2] [doc] alter table references bogus table-specific planner parameters https://commitfest.postgresql.org/27/2417/ Fixes for commit 6f3a13ff Should backpatch to v10. --- doc/src/sgml/ref/alter_table.sgml | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git a/doc/src/sgml/ref/alter_table.sgml b/doc/src/sgml/ref/alter_table.sgml index bae6e6a..67eddfb 100644 --- a/doc/src/sgml/ref/alter_table.sgml +++ b/doc/src/sgml/ref/alter_table.sgml @@ -714,9 +714,7 @@ WITH ( MODULUS numeric_literal, REM SHARE UPDATE EXCLUSIVE lock will be taken for fillfactor, toast and autovacuum storage parameters, as well as the - following planner related parameters: - effective_io_concurrency, parallel_workers, seq_page_cost, - random_page_cost, n_distinct and n_distinct_inherited. + parallel_workers planner parameter. -- 2.7.4 --5mjPmdht4ZehXHR2--