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 1pMoIQ-0007jA-6w for pgsql-docs@arkaria.postgresql.org; Tue, 31 Jan 2023 10:55:26 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pMoIN-0005Dr-ML for pgsql-docs@arkaria.postgresql.org; Tue, 31 Jan 2023 10:55:23 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pMb8X-0001Je-V7 for pgsql-docs@lists.postgresql.org; Mon, 30 Jan 2023 20:52:22 +0000 Received: from mail-wm1-x336.google.com ([2a00:1450:4864:20::336]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pMb8V-0005t3-Aa for pgsql-docs@lists.postgresql.org; Mon, 30 Jan 2023 20:52:21 +0000 Received: by mail-wm1-x336.google.com with SMTP id bg26so3098151wmb.0 for ; Mon, 30 Jan 2023 12:52:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:from:to:cc:subject:date:message-id :reply-to; bh=9hnAZWYdBl6vDsT1rqkUhfWNDrpRLpT66Z/AcBASPOA=; b=JnZr9tWSMwb0rSHzox5ATzlp3x3vErNtM/VyARE54mAgYWv6Zj7kaT6Eg9wFk7Zfox 2y91pj6nXJS3BDRPHMc1Wf+Ww//b4cYNdyoRfxB6/jtB5nD/e02q6vO18vN5KEE1ydAs 7XOTr9M4PL5RXNQZeFBhe79K4i2m/yhaPY3Z+ipn42oSCiZsIFyn+sr3iT7I98aN8Agd 6niC6CiBngo6cn3fTWycYKHADW8zw1k8Xza2G8Ae9a/0RhS34GvlWP8/JJ/CssDOqadE t8ZjuG7pjJjezziLnT2htFt11BLwKfM6Tx6oqtugY1nS80tYEt0yEzpOq6+y5IMky6rz RgIQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:from:references:to:content-language:subject:user-agent :mime-version:date:message-id:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=9hnAZWYdBl6vDsT1rqkUhfWNDrpRLpT66Z/AcBASPOA=; b=n8iUr9etAW7hqdSqufotpWfjiUpOVc3xIKtjyWG5GyBzMjyg43DQ+dP3LuRyYGdSpB eYIq/ztKD+CE36dnmIpueStPxoezFoOGnNYeINjCzidgcMOwbbC/2exF6C7isWmYBfCQ gAVJqa2FxHtJ9FfUsOqp6oQYud8xVnSEcf+QIEEJ/WWFzTZg4C0PBhxR83pOcnI7gdKy qyixhZcJW55YahF4sB2Jffx88JkhkdJeqFB9tzV2cEmOIwW0mK/pVVwmLQ49URwBYbpR HQ9sDRroRXKl6535e5VGZTsTyC8NEwFOOISohBxo+B13uEH6/kqnVugNOGygxVA4utq3 s6dA== X-Gm-Message-State: AO0yUKVA8wBrlcwoFdW8tevXkjfsigi30rBpx2KNPHOR27gKMdd10omi 3JswwaAQEPVTs8VSkk2wvJNBqkPu+eY= X-Google-Smtp-Source: AK7set9BvMlsNjmNFeTitAFY5ctJ6u2Orqs105nbAkRe7ewhjsMlsCccbwVQSsMNK/derGeIcr758w== X-Received: by 2002:a05:600c:6022:b0:3dc:5ad1:7a40 with SMTP id az34-20020a05600c602200b003dc5ad17a40mr4515450wmb.30.1675111936672; Mon, 30 Jan 2023 12:52:16 -0800 (PST) Received: from [192.168.0.50] (dynamic-78-8-193-148.ssp.dialog.net.pl. [78.8.193.148]) by smtp.googlemail.com with ESMTPSA id f9-20020a05600c4e8900b003d990372dd5sm19861945wmq.20.2023.01.30.12.52.15 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 30 Jan 2023 12:52:16 -0800 (PST) Content-Type: multipart/alternative; boundary="------------zsdyEdJtrJYV0S6fS7iPhyQD" Message-ID: Date: Mon, 30 Jan 2023 21:52:15 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: Suggestion for deprecated spellings Content-Language: pl-PL, en-US To: Bruce Momjian , pgsql-docs@lists.postgresql.org References: <167473556945.2667294.2003897901995802549@wrigleys.postgresql.org> From: =?UTF-8?Q?Tomis=c5=82aw_Kity=c5=84ski?= In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------zsdyEdJtrJYV0S6fS7iPhyQD Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit W dniu 30.01.2023 o 21:39, Bruce Momjian pisze: > On Thu, Jan 26, 2023 at 12:19:29PM +0000, PG Doc comments form wrote: >> The following documentation comment has been logged on the website: >> >> Page:https://www.postgresql.org/docs/12/sql-createrole.html >> Description: >> >> From time to time some spelling for given command gets obsolete, yet it is >> shown in the syntax on "equal rights" as other valid clauses. For instance >> see `CREATE ROLE` with deprecated spellings like `IN GROUP` or `USER`. I >> guess it would be useful to see those spellings visually marked as >> deprecated in Synopsis section (with e.g. strike-through or whatever suits >> better). Otherwise, when consulting documentation, it often requires jumping >> from the synopsis to detailed description and back to check if given >> spelling is still applicable. Just a thought. :-) > We don't need to show all _supported_ syntaxes in the "Synopsis" > section, so we could just remove them. > I like this idea even more! :-) Much cleaner approach . And then those obsolete aliases could be simply mentioned in the text for backward compatibility. Big yes! :-) -- Greetings, TK --------------zsdyEdJtrJYV0S6fS7iPhyQD Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: 8bit
W dniu 30.01.2023 o 21:39, Bruce Momjian pisze:
On Thu, Jan 26, 2023 at 12:19:29PM +0000, PG Doc comments form wrote:
The following documentation comment has been logged on the website:

Page: https://www.postgresql.org/docs/12/sql-createrole.html
Description: