On Mon, 6 Feb 2023 at 05:57, Tom Lane wrote:
> I'd hoped that some of these failures shared a root cause, but nope
> they were really four different bugs :-(. I've now pushed fixes
> for all four, and I hope you'll turn your fuzzer back on. This
> is very valuable testing.
Thanks Tom for fixing
Robins Tharakan writes:
> I'll probably switch off testing master for a day (and probably stop
> posting more on this thread), but thought I'd post one last
> (seemingly different) signature around the same commit, before
> I wrap up for the day.
I'd hoped that some of these failures shared a roo
Robins Tharakan writes:
> I'll probably switch off testing master for a day (and probably stop
> posting more on this thread), but thought I'd post one last
> (seemingly different) signature around the same commit, before
> I wrap up for the day.
Thanks for all the test cases! I remembered that
Hi Tom,
I'll probably switch off testing master for a day (and probably stop
posting more on this thread), but thought I'd post one last
(seemingly different) signature around the same commit, before
I wrap up for the day.
On Thu, 2 Feb 2023 at 23:25, Robins Tharakan wrote:
>
> To add, although
Thanks for taking a look.
To add, although a slightly different signature, it looks like Bug #17769 is
also related to this commit b448f1c8d83f.
https://www.postgresql.org/message-id/17769-e4f7a5c9d84a80a7%40postgresql.org
===
SQL
SELECT
FROM pg_catalog.pg_statio_all_tables AS ref_0,
LA
Robins Tharakan writes:
> This commit is causing occasional Asserts in my testing.
Thanks! I'm tired now, but will have a look tomorrow.
regards, tom lane
Hi Tom,
On Tue, 31 Jan 2023 at 05:43, Tom Lane wrote:
>
> Do assorted mop-up in the planner.
This commit is causing occasional Asserts in my testing.
SQL / Backtrace / triaging below.
Program terminated with signal SIGABRT, Aborted.
#0 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux
Do assorted mop-up in the planner.
Remove RestrictInfo.nullable_relids, along with a good deal of
infrastructure that calculated it. One use-case for it was in
join_clause_is_movable_to, but we can now replace that usage with
a check to see if the clause's relids include any outer join
that can n
