Re: AWS forcing PG upgrade from v9.6 a disaster

I tried 500, to no avail.  Since each change involves a delay as RDS readjusts, I'm going down a different path at the moment. On 2021-05-29 03:40, Lionel Bouton wrote: Le 29/05/2021 à 02:38, Dean Gibson (DB Administrator) a écrit : The original VACUUM FULL ANALYZE ran in 10 hours.  The plain A

Re: AWS forcing PG upgrade from v9.6 a disaster

On 5/29/21 3:59 PM, Dean Gibson (DB Administrator) wrote: > > > Meanwhile, I've been doing some checking.  If I remove "CAST( > license_status AS CHAR ) = 'A'", the problem disappears.  Changing the > JOIN to a RIGHT JOIN, & replacing WHERE with ON, also "solves" the > problem, but there is an ex

Re: AWS forcing PG upgrade from v9.6 a disaster

On 2021-05-28 22:24, Alexey M Boltenkov wrote: On 05/29/21 07:08, Dean Gibson (DB Administrator) wrote: [deleted] BTW what is the planner reason to not use index in v13.2? Is index in corrupted state? Have you try to reindex index "FccLookup"."_LicStatus_pkey" ? 1.5M of seqscan's are looking

Re: AWS forcing PG upgrade from v9.6 a disaster

On 2021-05-29 09:25, Adrian Klaver wrote: On 5/28/21 5:38 PM, Dean Gibson (DB Administrator) wrote: Can you repeat your EXPLAIN (ANALYZE, BUFFERS) of the query from your first post and post them here: https://explain.depesz.com/ Other information: 1) A diff of your configuration settings bet

Re: AWS forcing PG upgrade from v9.6 a disaster

On Fri, May 28, 2021, 22:41 Andrew Dunstan wrote: > > On 5/28/21 10:27 PM, Jan Wieck wrote: > > > > > > On Fri, May 28, 2021, 17:15 Andrew Dunstan > > wrote: > > > > > > > > > > AIUI he did an RDS upgrade. Surely that's not doing a dump/restore? I > > assume y