*SOLVED !!!* Below is the *new* EXPLAIN ANALYZE for *13.2* on AWS RDS
(with *no changes* to server parameters) along with the prior EXPLAIN
ANALYZE outputs for easy comparison.
While I didn't discount the significance & effect of optimizing the
server parameters, this problem always seemed to
> On May 30, 2021, at 20:07, Dean Gibson (DB Administrator)
> wrote:
> The first two JOINs are not the problem, & are in fact retained in my
> solution. The problem is the third JOIN, where "fips_county" from "County"
> is actually matched with the corresponding field from the "zip_code" VI
On 2021-05-30 20:41, Christophe Pettus wrote:
On May 30, 2021, at 20:07, Dean Gibson (DB Administrator)
wrote:
The first two JOINs are not the problem, & are in fact retained in my solution. The problem is the third JOIN,
where "fips_county" from "County" is actually matched with the correspo
"Dean Gibson (DB Administrator)" writes:
> I thought that having a "USING" clause, was semantically equivalent to
> an "ON" clause with the equalities explicitly stated. So no, I didn't
> try that.
USING is not that, or at least not only that ... read the manual.
I'm wondering if what you saw
On 2021-05-30 21:44, Tom Lane wrote:
"Dean Gibson (DB Administrator)" writes:
I thought that having a "USING" clause, was semantically equivalent to
an "ON" clause with the equalities explicitly stated. So no, I didn't
try that.
USING is not that, or at least not only that ... read the manual
