Re: AWS forcing PG upgrade from v9.6 a disaster
[
Date Prev
][
Date Next
][
Thread Prev
][
Thread Next
][
Date Index
][
Thread Index
]
Subject
: Re: AWS forcing PG upgrade from v9.6 a disaster
From
: Michael Lewis <mlewis@xxxxxxxxxxx>
Date
: Fri, 28 May 2021 14:11:09 -0600
Cc
: "Dean Gibson (DB Administrator)" <postgresql@xxxxxxxxxxx>, Andrew Dunstan <andrew@xxxxxxxxxxxx>, Pgsql Performance <pgsql-performance@xxxxxxxxxxxxxxxxxxxx>, lance@xxxxxxxxxxxx
In-reply-to
: <CAAWC1ohpyg-0ozzYW654HBgsbrOu9i7bfLuEU=nahAAtvh7MuQ@mail.gmail.com>
References
: <
88dec70b-eb63-0b72-0b5d-253851ef127b@mailpen.com
> <
9fa75894-d3be-e40b-cd89-f641bdf85df0@dunslane.net
> <
SN6PR11MB3326479A2100FF2A578CD1FCDE229@SN6PR11MB3326.namprd11.prod.outlook.com
> <CAAWC1ohpyg-0ozzYW654HBgsbrOu9i7bfLuEU=nahAAtvh7MuQ@mail.gmail.com>
The plan is also influenced by cost related and memory related config settings such as random_page_cost and work_mem, right? Hence the questions if configs are matching or newer versions are using very conservative (default) settings.
References
:
AWS forcing PG upgrade from v9.6 a disaster
From:
Dean Gibson (DB Administrator)
Re: AWS forcing PG upgrade from v9.6 a disaster
From:
Andrew Dunstan
Re: AWS forcing PG upgrade from v9.6 a disaster
From:
Campbell, Lance
Re: AWS forcing PG upgrade from v9.6 a disaster
From:
Ryan Bair
Prev by Date:
Re: AWS forcing PG upgrade from v9.6 a disaster
Next by Date:
Re: AWS forcing PG upgrade from v9.6 a disaster
Previous by thread:
Re: AWS forcing PG upgrade from v9.6 a disaster
Next by thread:
Re: AWS forcing PG upgrade from v9.6 a disaster
Index(es):
Date
Thread
[Postgresql General]
[Postgresql PHP]
[PHP Users]
[PHP Home]
[PHP on Windows]
[Kernel Newbies]
[PHP Classes]
[PHP Books]
[PHP Databases]
[Yosemite]
