| From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Brad White <b55white(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Upgrading to v12 |
| Date: | 2022-11-29 02:23:34 |
| Message-ID: | ce8f88d5-9bc6-ea1d-8f21-40d2a59bccc6@aklaver.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 11/28/22 17:02, Tom Lane wrote:
> Brad White <b55white(at)gmail(dot)com> writes:
>> 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?
>
> If you can connect to the new installation, then you're done with
> that part, and can get on with the dump-and-restore part.
Yeah this is coming from this SO question:
Brad was double clutching on the initdb.
>
> regards, tom lane
>
>
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | rajesh singarapu | 2022-11-29 02:29:03 | Re: Support logical replication of DDLs |
| Previous Message | Tom Lane | 2022-11-29 01:02:19 | Re: Upgrading to v12 |