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 1mwige-0007Wj-LD for pgsql-docs@arkaria.postgresql.org; Mon, 13 Dec 2021 10:36:04 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mwigd-0001my-1w for pgsql-docs@arkaria.postgresql.org; Mon, 13 Dec 2021 10:36:03 +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 1mwigc-0001mp-CZ for pgsql-docs@lists.postgresql.org; Mon, 13 Dec 2021 10:36:02 +0000 Received: from wout4-smtp.messagingengine.com ([64.147.123.20]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mwigU-0002d1-UQ for pgsql-docs@postgresql.org; Mon, 13 Dec 2021 10:36:01 +0000 Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 186413200708; Mon, 13 Dec 2021 05:35:52 -0500 (EST) Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 13 Dec 2021 05:35:53 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=4byXKXvacZ7LX80j976LNQ2/XvZY7lELI7HJ9HRcD yQ=; b=SdmYzmVFT8O+I9Si5fGEf6/Gc4ln04xhQCyZ7CSkgYnqXGoeCtBNPMXuI 9+9xdWSk2JzG4pW0B+ePBJwzel7qxPpU2YDXnh/ruExzFh/z3gMnRcQBChafYtL0 mTgJgMPc5Z+IjLq7yeJ7PmJggPBa3/LPpzBZw5dWc5onXM4Cu+QThF4QKCBtLjoF O3ya3mNpagKABdKK1ry4OYrhgeQYzFqzx5VZd5TC1jKtNNPHDyQ/VuMw5WoZC/Q8 GpfqGPe7uGUC8N0q8It3Yyb4JRWl5jHfN5bDPD845/JgktlIbtlUKrGN9zrRgQHR TQiqo/34rVaTWRAfdNB1OqFpDyncg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvuddrkeekgddukecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpefkffggfgfuvfhfhfgjtgfgsehtjeertddtfeejnecuhfhrohhmpefrvghtvghr ucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnthgvrh hprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpeffvefgueduueelieeufeej vdfhffettddtudegvdeuuedtuddvhedvheffudejhfenucffohhmrghinhepphhoshhtgh hrvghsqhhlrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghi lhhfrhhomhepphgvthgvrhdrvghishgvnhhtrhgruhhtsegvnhhtvghrphhrihhsvggusg drtghomh X-ME-Proxy: Received: by mail.messagingengine.com (Postfix) with ESMTPA; Mon, 13 Dec 2021 05:35:51 -0500 (EST) Message-ID: <236bee0a-b624-b35d-516a-da7e4c3d2358@enterprisedb.com> Date: Mon, 13 Dec 2021 11:35:49 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:91.0) Gecko/20100101 Thunderbird/91.3.2 Subject: Re: bad style for SECURITY DEFINER Content-Language: en-US To: Justin Pryzby , pgsql-docs@postgresql.org References: <20211213001707.GR17618@telsasoft.com> From: Peter Eisentraut In-Reply-To: <20211213001707.GR17618@telsasoft.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 13.12.21 01:17, Justin Pryzby wrote: > The title of this section looks poor in the first two web browsers I tried. > https://www.postgresql.org/docs/current/sql-createfunction.html#id-1.9.3.67.10.2 > | Writing SECURITY DEFINER Functions Safely This appears to be a web site styling issue. It looks more reasonable when I use the default style.