Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rh87D-009l6W-27 for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 13:12:23 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rh87B-007x55-Lb for pgsql-www@arkaria.postgresql.org; Mon, 04 Mar 2024 13:12:22 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rh87B-007x2b-98 for pgsql-www@lists.postgresql.org; Mon, 04 Mar 2024 13:12:21 +0000 Received: from mail-ej1-x62d.google.com ([2a00:1450:4864:20::62d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rh876-002iyP-9R for pgsql-www@postgresql.org; Mon, 04 Mar 2024 13:12:21 +0000 Received: by mail-ej1-x62d.google.com with SMTP id a640c23a62f3a-a44d084bfe1so251157266b.1 for ; Mon, 04 Mar 2024 05:12:15 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=f10-com-br.20230601.gappssmtp.com; s=20230601; t=1709557935; x=1710162735; darn=postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=OQ1geY3Xi5WrcZdOl3F9PjJ1R5bfTJ48e5Pqb4O6m0I=; b=kdFmdSIdGdwAkPITLWAjJpCg2gifTQE8YivBmciOpD0ugkcvalsQLXGNxbuGnsmObe BY4UmQkp7oTQ8BFOE84TUEsw005XvlMEGS8D1s8+WZFZ/m6Gv2Eoq3WuLim9F+3VdSDl UMhm1GMWek9hCI2iyo+8TcS3ge9AJgdr10f8pUxCYGzyDvTQ23X+cuQXs7Qvu0piqxJf Pj+LK9NUG/Wwr61LY5do4xPgTapenvIB4Pqk2rsF0OQbplNoq51IyTNOcvemDAkKmXXf FHMZssRycmtsBMreFH2XR7iTAMXXiYuT260dL9W6WQbmk2OTw29sk5uEM+w1pGx2IM9V BcnQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1709557935; x=1710162735; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=OQ1geY3Xi5WrcZdOl3F9PjJ1R5bfTJ48e5Pqb4O6m0I=; b=lO8EHH+wgeiXia9frtldgWj3pQAbMhJgDVqfIxugFp+c1vyuQJHQrWkrjUe7YxIlw9 5j1lSJZRep2P5A6o9azjm7h0WUW9Aj4kp5vzJ8DT6DMwUwInA8SYCepkoBg9KYJP3YbZ tEUdWgovNiHbe6NaLm2G+/f2MTBuzaJD2XE3tsEULqhgqcLaoMYX9RETHt9KEHIkpr/u iilfbfijwgpFXyXPzZhmaXUzOW8MhqVBNYxs9TXKtdeTF1H4BUtHuWI7fgrqH9s6QbIP GlEfcFJk3hwrdS0zgZOSrncwiARekB5zMhCTUfccuIcvt0jPNwlULwk/WKr0NG4HlZ3T 9+GA== X-Gm-Message-State: AOJu0YwWgwD/7vyIwyiJbY0qsKvXub+EvU4xseH83jo4R9yQWpVtDfJc t66P+BQ3/Tuf1U16FRpL+Hcc5puTBRg1tflGd2AoolSRhKDg+sr1WAV6qGskwoPsD2Cdmy8VWgm b34XIDoC5RGeQ7s9e/8iXyNfrxX7Pn8WOGkPzQqCK6Qhlx4QFEA== X-Google-Smtp-Source: AGHT+IENH7BJB4ogXUDZGggES9IGLFfvIaYMhfKfJOhb+xIeUXO85LO3YIhzmjFsQ8hzLdEyuYABD5ToYB75oHliWEo= X-Received: by 2002:a17:906:24d4:b0:a40:3aa3:9b8a with SMTP id f20-20020a17090624d400b00a403aa39b8amr6572732ejb.15.1709557934737; Mon, 04 Mar 2024 05:12:14 -0800 (PST) MIME-Version: 1.0 References: <202403021444.yyabqn4eatpx@alvherre.pgsql> In-Reply-To: <202403021444.yyabqn4eatpx@alvherre.pgsql> From: Marcos Pegoraro Date: Mon, 4 Mar 2024 10:11:26 -0300 Message-ID: Subject: Re: Diff of this page with other version To: Alvaro Herrera Cc: pgsql-www@postgresql.org Content-Type: multipart/alternative; boundary="0000000000006c62660612d579df" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000006c62660612d579df Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Em dom., 3 de mar. de 2024 =C3=A0s 17:26, Alvaro Herrera escreveu: > > I think your proposal is a reasonable idea and a very convenient service > for users ... but there's zero chance that committers are going to > accept the additional work and the resulting uglification of the > document source. > > If it can be done by post-processing the XML and finding the > differences, to automatically insert some markup that lets the UI show > the differences as you suggest, then we can discuss ways to integrate > that. I understand your point but cannot imagine a tool that does all those points I've detailed. And about uglification of document source, what I propose is just another internal tag for each version. same way you use , , etc, you would use , and so on, just that. So I don't think it is a uglification of document source. Version 15: You must own the schema to use ALTER SCHEMA. To rename a schema you must also have the CREATE privilege for the database. To alter the owner, you must also be a direct or indirect member of the new owning role, and you must have the CREATE privilege for the database. (Note that superusers have all these privileges automatically.) Version 16: ** You must own the schema to use ALTER SCHEMA. To rename a schema you must also have the CREATE privilege for the database. To alter the owner, you must be able to SET ROLE to the new owning role, and that role must have the CREATE privilege for the database. (Note that superusers have all these privileges automatically.) ** --0000000000006c62660612d579df Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Em dom., 3 de mar. de 2= 024 =C3=A0s 17:26, Alvaro Herrera <alvherre@alvh.no-ip.org> escreveu:
I think your proposal is a reasonable idea and a very convenient service for users ... but there's zero chance that committers are going to
accept the additional work and the resulting uglification of the
document source.

If it can be done by post-processing the XML and finding the
differences, to automatically insert some markup that lets the UI show
the differences as you suggest, then we can discuss ways to integrate
that.

I understand your point = but cannot imagine a tool that does all=C2=A0those points I've detailed= .
And about uglification of document source, what I = propose is just another internal tag=C2=A0
for each = version. same way you use <command>, <literal>, etc, you would = use <v15>,=C2=A0
<v16> and so on, just t= hat. So I don't think it is a=C2=A0uglification of document source.

Version 15:
=C2=A0 <para>
=C2=A0 =C2=A0You must own the schema to use = <command>ALTER SCHEMA</command>.
=C2=A0 =C2=A0To rename a sc= hema you must also have the
=C2=A0 =C2=A0<literal>CREATE</liter= al> privilege for the database.
=C2=A0 =C2=A0To alter the owner, you = must also be a direct or
=C2=A0 =C2=A0indirect member of the new owning = role, and you must have the
=C2=A0 =C2=A0<literal>CREATE</liter= al> privilege for the database.
=C2=A0 =C2=A0(Note that superusers ha= ve all these privileges automatically.)
=C2=A0 </para>
=C2=A0&l= t;/refsect1>
Version 16:
=C2=A0 <para><v16>
=C2=A0 =C2=A0You must own = the schema to use <command>ALTER SCHEMA</command>.
=C2=A0 = =C2=A0To rename a schema you must also have the
=C2=A0 =C2=A0<literal= >CREATE</literal> privilege for the database.
=C2=A0 =C2=A0To a= lter the owner, you must be able to <literal>SET ROLE</literal>= to the
=C2=A0 =C2=A0new owning role, and that role must have the
=C2= =A0 =C2=A0<literal>CREATE</literal> privilege for the database.=
=C2=A0 =C2=A0(Note that superusers have all these privileges automatica= lly.)
=C2=A0 </v16></para>
=C2= =A0</refsect1>
--0000000000006c62660612d579df--