6 cluster before you tried to upgrade
from it?
No, I don't remember anything specific about it.
2018-06-10 23:55 GMT+03:00 Adrian Klaver :
> On 06/10/2018 01:46 PM, Alexander Shutyaev wrote:
>
>> I can provide you with more info. Please tell me what you need. I really
>>
tes:
> > On 06/09/2018 03:46 AM, Alexander Shutyaev wrote:
> >> The upgrade operation failed after several hours with the following
> error:
> >> database is not accepting commands to avoid wraparound data loss in
> >> database with OID 0
>
> > Do you know which
I can provide you with more info. Please tell me what you need. I really hope
someone here can help me somehow solve or workaround this, because I really
need to migrate to v10 for its features.
Thanks in advance,
Alexander
--
Sent from:
a very big oid (can that seem
strange?) and its oid has changed.
select oid, datname from pg_database;
oid | datname
---+---
13011 | template0
16400 | bof
13012 | postgres
16401 | sslentry
1 | template1
(5 rows)
2018-06-11 0:03 GMT+03:00 Alexander Shutyaev :
> No datab
Back again,
>> Alexander, could you hack things up so autovacuum logging is enabled
>> (log_autovacuum_min_duration=0), and see whether it's triggered?
I've changed this config setting in both 9.6 and 10.4 postgresql.conf, then
I've ran pg_upgrade once more.
However I'm not sure how can I see
ust be vacuumed within nnn
transactions" number.
As for the prepared transactions - no, I don't have them, our application
doesn't use this functionality.
2018-06-11 0:34 GMT+03:00 Adrian Klaver :
> On 06/10/2018 02:09 PM, Alexander Shutyaev wrote:
>
>> Some more notes on databse
I'm back with more details.
First, I've deleted the smaller sslentry database, since I don't need it,
just so that it doesn't somehow spoil the picture. Now there is only 1 user
database - bof (OID=16400). After that I've ran the pg_upgrade on a clean
10.4 cluster and it failed in the same way.
ase and ran your query. The
result is attached in 96-query1-template0.txt.
2018-06-11 22:10 GMT+03:00 Adrian Klaver :
> On 06/11/2018 11:32 AM, Alexander Shutyaev wrote:
>
>> I'm back with more details.
>>
>> First, I've deleted the smaller sslentry database, since I don't nee
Did you check this view to confirm?
Yes, I did:
select * from pg_prepared_xacts;
transaction | gid | prepared | owner | database
-+-+--+---+--
(0 rows)
2018-06-11 3:15 GMT+03:00 Adrian Klaver :
> On 06/10/2018 02:45 PM, Alexander Shutyaev wrote:
>
> C
Hello!
I've been trying to upgrade a postgresql cluster from 9.6 to 10. I've
executed the pg_upgrade with the following options:
/usr/lib/postgresql/10/bin/pg_upgrade -b /usr/lib/postgresql/9.6/bin/ -B
/usr/lib/postgresql/10/bin/ -d /var/lib/postgresql/9.6/main -D
/var/lib/postgresql/10/main -o
as to how can I decrease time needed for pg_dumpall
| psql?
Thanks in advance!
2018-06-13 0:11 GMT+03:00 Alexander Shutyaev :
> Back again,
>
> >> Alexander, could you hack things up so autovacuum logging is enabled
> >> (log_autovacuum_min_duration=0), and see whether it's tri
11 matches
Mail list logo
