From: | Greg Smith <greg(dot)smith(at)crunchydata(dot)com> |
---|---|
To: | Christoph Berg <myon(at)debian(dot)org>, Greg Smith <greg(dot)smith(at)crunchydata(dot)com>, pgsql-pkg-debian(at)postgresql(dot)org |
Subject: | Re: PostGIS files for PG17-b2 |
Date: | 2024-07-01 16:51:00 |
Message-ID: | CAHo4unZh9CaarJ-cc90SwfrGyVUu4mROj3w+sqbwfwmBKgkjgw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-pkg-debian |
On Mon, Jul 1, 2024 at 12:16 PM Christoph Berg <myon(at)debian(dot)org> wrote:
> > postgres(at)rising:~/pgbench-tools$ rm -rf /var/tmp/postgresql-17-202405161
> > 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.
From | Date | Subject | |
---|---|---|---|
Next Message | Christoph Berg | 2024-07-03 10:39:51 | Re: PostGIS files for PG17-b2 |
Previous Message | Christoph Berg | 2024-07-01 16:16:03 | Re: PostGIS files for PG17-b2 |