From: | Brad White <b55white(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
Subject: | Re: Upgrading to v12 |
Date: | 2022-11-29 00:02:41 |
Message-ID: | CAA_1=91QfQS0EGYUzpqz=KDRKUeU3vEzJWnrTmoJrgWEPQ82MA@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
Tom,
I tried to run initdb after re-installing pg 12
using postgresql-12.10-2-windows-x64.exe.
But the runas I'm using to execute it as pguser seems to be swallowing all
the output, so I can't see any errors.
I was able to run pg_checksums and get those enabled.
Is there anything else I want from initdb?
Or can I skip that?
On Fri, Nov 11, 2022 at 4:27 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Nonetheless,
> your path forward is clear: use pg_dump (or better pg_dumpall)
> and then load the output into a *freshly initdb'd v12 installation.*
> It'll be a bit slower than the pg_upgrade way, but it'll work.
>
> regards, tom lane
>
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2022-11-29 01:02:19 | Re: Upgrading to v12 |
Previous Message | Kirk Wolak | 2022-11-28 22:22:19 | Re: Getting PSQL in Windows to support TAB/Autocomplete via modified readline... |