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

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?

On 7/5/25 12:19, Pierre Fortin wrote: On Sat, 05 Jul 2025 14:30:20 -0400 Tom Lane wrote: I'd say give it a try; be sure to use one of the pg_dump modes that compress the data. OK... I failed to mention I have several databases in this cluster; so digging into pg_dumpall, I see: --binar

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

On 7/5/25 12:19, Pierre Fortin wrote: 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 82279106

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

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/db You said you have ~70TB of free space, so where is the other ~63TB?

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

On Sat, Jul 5, 2025 at 3:19 PM Pierre Fortin wrote: > 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? > > > >>

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

Pierre Fortin writes: > OK... I failed to mention I have several databases in this cluster; so > digging into pg_dumpall, I see: >--binary-upgrade > This option is for use by in-place upgrade utilities. Its use for > other purposes is not recommended or supported. The behavior of the

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

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

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

On Sat, Jul 5, 2025 at 2:24 PM wrote: > On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote: > > >On 7/5/25 09:52, Pierre Fortin wrote: > > >> 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

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

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/data It's likely that there's a deal of bloat in that. Even if there's not much bloat, this number will include indexes

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

On Sat, 5 Jul 2025 11:11:32 -0700 Adrian Klaver wrote: >On 7/5/25 09:52, Pierre Fortin wrote: >> 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

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

On Sat, Jul 5, 2025 at 2:11 PM Adrian Klaver wrote: > On 7/5/25 09:52, Pierre Fortin wrote: > > 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.mg

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

On 7/5/25 09:52, Pierre Fortin wrote: 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

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

On Sat, 05 Jul 2025 13:04:55 -0400 Tom Lane wrote: >You cannot do pg_upgrade without a copy of the old postgres >server binary as well as the new one. Bummer. Wish I had skills & time to try to overcome this... Thanks! Pierre

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

Pierre Fortin writes: > - my Linux distro (Mageia) is not setup to handle multiple versions of > postgres (installing 17.5 removes 15.13). Ugh. You cannot do pg_upgrade without a copy of the old postgres server binary as well as the new one. pg_upgrade by itself is not capable of accessing ei

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

On Sat, Jul 5, 2025 at 9:52 AM Pierre Fortin wrote: > If new pg_upgrade is the only binary, will both -b and -B default to it? > Maybe at minimum I may need to specify: > $ pg_upgrade -b /usr/bin -d data15 -D data17 -k > > pgsql/pgsql-18/bin > ./pg_ctl -D /var/pgsql/postgres-17 start waiting for

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

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: Foreign Data Wrapper from Oracle to Postgres 16

Hi, We found a link that may help resolve the issue you encountered while creating the oracle_fdw extension on windows machine. laurenz/oracle_fdw: PostgreSQL Foreign Data Wrapper for Oracle [https://opengraph.githubassets