From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | David Rowley <dgrowleyml(at)gmail(dot)com> |
Cc: | Onder Kalaci <onderk(at)microsoft(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Assertion failure with LEFT JOINs among >500 relations |
Date: | 2020-10-19 00:06:55 |
Message-ID: | 247336.1603066015@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
David Rowley <dgrowleyml(at)gmail(dot)com> writes:
> It would be good to hear Onder's case to see if he has a good argument
> for having a vested interest in pg13 not failing this way with assets
> enabled.
Yeah, some context for this report would be a good thing.
(BTW, am I wrong to suppose that the same case fails the same
way in our older branches? Certainly that Assert has been there
a long time.)
> I guess we could resolve that concern by just changing the failing
> assert to become: Assert(outer_skip_rows <= outer_rows ||
> isinf(outer_rows));
I can't really object to just weakening the Assert a tad.
My thoughts would have run towards checking for the NaN though.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Rowley | 2020-10-19 00:18:43 | Re: Assertion failure with LEFT JOINs among >500 relations |
Previous Message | David Rowley | 2020-10-18 23:37:49 | Re: Assertion failure with LEFT JOINs among >500 relations |