Re: pg_upgrade: can I use same binary for old & new?

2025-07-05 Thread Pierre Fortin
On Sat, 5 Jul 2025 12:58:10 -0700 Adrian Klaver wrote: >On 7/5/25 11:24, p...@pfortin.com wrote: >> On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote: >> > >> Didn't try given: >> $ df /mnt/db >> Filesystem Size Used Avail Use% Mounted on >> /dev/sdh117T 13T 3.0T 82% /mnt/

Re: pg_upgrade: can I use same binary for old & new?

2025-07-05 Thread Pierre Fortin
On Sat, 05 Jul 2025 14:30:20 -0400 Tom Lane wrote: Forgive my ignorance; always trying to learn more... :) >p...@pfortin.com writes: >> On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote: >>> How did you measure above? > >> # du -sb /var/lib/pgsql/data >> 8227910662297 /var/lib/pgsql/dat

pg_upgrade: can I use same binary for old & new?

2025-07-05 Thread Pierre Fortin
Hi, [Hope this gets through after dumping DKIM-ignorant mail provider.] Wanting to upgrade from: PostgreSQL 15.13 on x86_64-mageia-linux-gnu, compiled by gcc (Mageia 15.1.0-1.mga10) 15.1.0, 64-bit to: PG 17.5 Way back, I was able to use -k|--link option on pg_upgrade (PG13 to PG15); but since

Re: cache lookup failed for function 0

2023-09-30 Thread Pierre Fortin
Ignore this message; I wondered where it went to -- Looks like I accidentally hit Ctrl+Enter; just did that to another... SIGH... On Sat, 30 Sep 2023 09:30:08 -0400 p...@pfortin.com wrote: >On Fri, 29 Sep 2023 14:27:48 -0700 Adrian Klaver wrote: