pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Jonathan S. Katz <jkatz@postgresql.org>
To: Justin Pryzby <pryzby@telsasoft.com>
To: Daniel Gustafsson <daniel@yesql.se>
Cc: Peter Eisentraut <peter.eisentraut@enterprisedb.com>
Cc: pgsql-www@postgresql.org
Subject: Re: bad style for SECURITY DEFINER
Date: Mon, 13 Dec 2021 16:33:05 -0500
Message-ID: <3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org> (raw)
In-Reply-To: <20211213140110.GU17618@telsasoft.com>
References: <20211213001707.GR17618@telsasoft.com>
	<236bee0a-b624-b35d-516a-da7e4c3d2358@enterprisedb.com>
	<212DF319-94A5-4827-9F78-74D29C888717@yesql.se>
	<20211213140110.GU17618@telsasoft.com>

On 12/13/21 9:01 AM, Justin Pryzby wrote:
> On Mon, Dec 13, 2021 at 02:11:24PM +0100, Daniel Gustafsson wrote:
>>> On 13 Dec 2021, at 11:35, Peter Eisentraut <peter.eisentraut@enterprisedb.com> wrote:
>>>
>>> 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

The below seems to do the trick. Tested in Chrome, FF, and Safari. 
Screenshot attached.

If no objections I'll push the patch tomorrow.

Thanks,

Jonathan

diff --git a/media/css/main.css b/media/css/main.css
index d97da4d..955f612 100644
--- a/media/css/main.css
+++ b/media/css/main.css
@@ -877,6 +877,10 @@ code,
    font-size: inherit !important;
  }

+#docContent h2 code {
+  margin: 0.5em;
+}
+
  #docContent .NAVHEADER table th,
  #docContent .navheader table th {
    text-align: center;



Attachments:

  [image/png] Screen Shot 2021-12-13 at 4.32.24 PM.png (25.9K, ../3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org/2-Screen%20Shot%202021-12-13%20at%204.32.24%20PM.png)
  download | view image

  [application/pgp-signature] OpenPGP_signature (839B, ../3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org/3-OpenPGP_signature)
  download

view thread (9+ messages)  latest in thread

Message-ID: <3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org>
Permalink:  ../3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org/
Also on:    postgresql.org/message-id/3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-docs@postgresql.org
  Cc: jkatz@postgresql.org, pryzby@telsasoft.com, daniel@yesql.se, peter.eisentraut@enterprisedb.com, pgsql-www@postgresql.org
  Subject: Re: bad style for SECURITY DEFINER
  In-Reply-To: <3686660c-02a4-7b06-98e9-34a30bb7be08@postgresql.org>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox