From: | Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com> |
---|---|
To: | Dávid Suchan <david(dot)suchan(dot)ds(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: pg_upgradecluster transfering only a portion of the data |
Date: | 2023-02-27 17:44:28 |
Message-ID: | f59934aa-3f06-b57c-17eb-1165e6f99091@aklaver.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 2/27/23 09:10, Adrian Klaver wrote:
> On 2/27/23 09:05, Dávid Suchan wrote:
>
> Please use Reply All
> Ccing list
>
>> My bad,
>> \l+ lists databases and their respective sizes- I used that and also
>> pg_size_pretty(), the result size was the same - before it was 20gb
>> for the biggest db, after it was 700mb.
>> I counted rows before the upgrade in one of the biggest and most
>> important table that I was watching and comparing - before there were
>> hundreds of thousands or millions of rows(not sure about the exact
>> number, just a lot), after the upgrade only like 15, but the first 15
>> rows matched after the upgrade when I checked with select of that table.
Hmm, I can't see how you got that state without there being some sort of
error messages.
Just to be clear:
1) The 9.6 and 14 instances where installed from the same source?
2) Are you using tablespaces other then the default?
Scan the Postgres log for the 14 instance at /var/log/postgresql for
error messages.
--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com
From | Date | Subject | |
---|---|---|---|
Next Message | Dávid Suchan | 2023-02-27 17:50:13 | Re: pg_upgradecluster transfering only a portion of the data |
Previous Message | Laurenz Albe | 2023-02-27 17:40:57 | Re: pg_upgradecluster transfering only a portion of the data |