MIME-Version: 1.0
References: 
 <CAHo4unZmXujaaV9npNmEMQw26jaCH7=+2+hUuJjNkCN3WnOo7A@mail.gmail.com>
 <ZoLWQ7txLAyyFKZ_@msg.df7cb.de>
In-Reply-To: <ZoLWQ7txLAyyFKZ_@msg.df7cb.de>
From: Greg Smith <greg.smith@crunchydata.com>
Date: Mon, 1 Jul 2024 12:51:00 -0400
Message-ID: 
 <CAHo4unZh9CaarJ-cc90SwfrGyVUu4mROj3w+sqbwfwmBKgkjgw@mail.gmail.com>
Subject: Re: PostGIS files for PG17-b2
To: Christoph Berg <myon@debian.org>, Greg Smith <greg.smith@crunchydata.com>,
	pgsql-pkg-debian@postgresql.org
Content-Type: multipart/alternative; boundary="0000000000008fca16061c326793"
Archived-At: 
 <https://www.postgresql.org/message-id/CAHo4unZh9CaarJ-cc90SwfrGyVUu4mROj3w%2BsqbwfwmBKgkjgw%40mail.gmail.com>
Precedence: bulk

--0000000000008fca16061c326793
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Mon, Jul 1, 2024 at 12:16=E2=80=AFPM Christoph Berg <myon@debian.org> wr=
ote:

> > postgres@rising:~/pgbench-tools$ rm -rf /var/tmp/postgresql-17-20240516=
1
> > rm: cannot remove '/var/tmp/postgresql-17-202405161/bin/pg_resetwal':
> > Permission denied
>
> Hmm. I had thought that the other steps would already require root,
> but pg_upgradecluster and friends do mostly work without. I'm unsure
> if I want to prefix every command with "sudo" since the instructions
> look scary enough already.
>

I was able to do all the other upgrade steps as the postgres user.   If the
temporary binaries were installed in the postgres user's home directory
instead, the whole thing might be possible to do as postgres.  Not sure
what the downsides would be to relocating that block of binaries.  It's
really not an important problem to solve, since the catversion bump in the
middle of release tweaking is a development only part of upgrading,
Anyone running into this should be capable of sorting out when they need
sudo.  Just passing along the feedback.

Thanks for answering the PostGIS question, I will move onto other tests
while waiting for that to resolve.

--0000000000008fca16061c326793
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jul 1, 2024 at 12:16=E2=80=AFPM C=
hristoph Berg &lt;<a href=3D"mailto:myon@debian.org">myon@debian.org</a>&gt=
; wrote:</div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" =
style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pa=
dding-left:1ex">&gt; postgres@rising:~/pgbench-tools$ rm -rf /var/tmp/postg=
resql-17-202405161<br>
&gt; rm: cannot remove &#39;/var/tmp/postgresql-17-202405161/bin/pg_resetwa=
l&#39;:<br>
&gt; Permission denied<br>
<br>
Hmm. I had thought that the other steps would already require root,<br>
but pg_upgradecluster and friends do mostly work without. I&#39;m unsure<br=
>
if I want to prefix every command with &quot;sudo&quot; since the instructi=
ons<br>
look scary enough already.<br></blockquote><div><br></div><div>I was able t=
o do all the other upgrade steps as the postgres user. =C2=A0 If the tempor=
ary binaries were installed in the postgres user&#39;s home directory inste=
ad, the whole thing might be possible to do as postgres.=C2=A0 Not sure wha=
t the downsides would be to relocating that block of binaries.=C2=A0 It&#39=
;s really not an important problem to solve, since the catversion bump in t=
he middle of release tweaking is a development only part of upgrading,=C2=
=A0=C2=A0 Anyone running into this should be capable of sorting out when th=
ey need sudo.=C2=A0 Just passing along the feedback.</div><div><br></div><d=
iv>Thanks for answering the PostGIS question, I will move onto other tests =
while waiting for that to resolve.</div></div></div>

--0000000000008fca16061c326793--