| From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
|---|---|
| To: | "Dean Gibson (DB Administrator)" <postgresql(at)mailpen(dot)com>, pgsql-performance(at)postgresql(dot)org |
| Subject: | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Date: | 2021-05-29 20:35:27 |
| Message-ID: | 5d3aa25f-a886-a3e8-ba1c-9d31c30a21c3@dunslane.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-performance |
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 extra row where license_status is NULL, due
> to the RIGHT JOIN. Currently trying to figure that out (why did the
> CAST ... match 'A', if it is null?)...
Why are you using this expression? It's something you almost never want
to do in my experience. Why not use the substr() function to get the
first character?
cheers
andrew
--
Andrew Dunstan
EDB: https://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2021-05-29 22:34:57 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-05-29 19:59:47 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Lewis | 2021-05-29 22:34:57 | Re: AWS forcing PG upgrade from v9.6 a disaster |
| Previous Message | Dean Gibson (DB Administrator) | 2021-05-29 20:17:40 | Re: AWS forcing PG upgrade from v9.6 a disaster |