New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[YSQL][randgen] Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346 #21292
Labels
Comments
mtakahar
added
area/ysql
Yugabyte SQL (YSQL)
status/awaiting-triage
Issue awaiting triage
labels
Mar 4, 2024
yugabyte-ci
added
kind/bug
This issue is a bug
priority/medium
Medium priority issue
labels
Mar 4, 2024
mtakahar
changed the title
[YSQL][randgen] Invalid memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
[YSQL][randgen] Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
Mar 4, 2024
mtakahar
changed the title
[YSQL][randgen] Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
[YSQL][randgen] REGRESSION: Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
Mar 4, 2024
mtakahar
changed the title
[YSQL][randgen] REGRESSION: Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
[YSQL][randgen] Memory conetxt assertion failure: MemoryContextReset + 102 at .../src/postgres/src/backend/utils/mmgr/mcxt.c:346
Mar 14, 2024
tanujnay112
added a commit
that referenced
this issue
Mar 15, 2024
Summary: This change fixes a bug where we would not detect some unbatchable filters when forming an indexpath if the indexpath acceptable batched values from more than one relation. Needs backports to 2.20 and 2.18 Jira: DB-10208 Test Plan: ./yb_buid.sh --java-test "org.yb.pgsql.TestPgRegressJoin' Reviewers: mtakahara Reviewed By: mtakahara Subscribers: yql Differential Revision: https://phorge.dev.yugabyte.com/D33179
asrinivasanyb
pushed a commit
to asrinivasanyb/yugabyte-db
that referenced
this issue
Mar 18, 2024
Summary: This change fixes a bug where we would not detect some unbatchable filters when forming an indexpath if the indexpath acceptable batched values from more than one relation. Needs backports to 2.20 and 2.18 Jira: DB-10208 Test Plan: ./yb_buid.sh --java-test "org.yb.pgsql.TestPgRegressJoin' Reviewers: mtakahara Reviewed By: mtakahara Subscribers: yql Differential Revision: https://phorge.dev.yugabyte.com/D33179
tanujnay112
added a commit
that referenced
this issue
Mar 22, 2024
Summary: Original commit: ad87ceb / D33179 This change fixes a bug where we would not detect some unbatchable filters when forming an indexpath if the indexpath acceptable batched values from more than one relation. Needs backports to 2.20 and 2.18 Jira: DB-10208 Test Plan: ./yb_buid.sh --java-test "org.yb.pgsql.TestPgRegressJoin' Reviewers: mtakahara Reviewed By: mtakahara Subscribers: yql Tags: #jenkins-ready Differential Revision: https://phorge.dev.yugabyte.com/D33228
tanujnay112
added a commit
that referenced
this issue
Mar 22, 2024
Summary: Original commit: ad87ceb / D33179 This change fixes a bug where we would not detect some unbatchable filters when forming an indexpath if the indexpath acceptable batched values from more than one relation. Needs backports to 2.20 and 2.18 Jira: DB-10208 Test Plan: ./yb_buid.sh --java-test "org.yb.pgsql.TestPgRegressJoin' Reviewers: mtakahara Reviewed By: mtakahara Subscribers: yql Tags: #jenkins-ready Differential Revision: https://phorge.dev.yugabyte.com/D33199
tanujnay112
added a commit
that referenced
this issue
Mar 22, 2024
Summary: Original commit: ad87ceb / D33179 This change fixes a bug where we would not detect some unbatchable filters when forming an indexpath if the indexpath acceptable batched values from more than one relation. Needs backports to 2.20 and 2.18 Jira: DB-10208 Test Plan: ./yb_buid.sh --java-test "org.yb.pgsql.TestPgRegressJoin' Reviewers: mtakahara Reviewed By: mtakahara Subscribers: yql Tags: #jenkins-ready Differential Revision: https://phorge.dev.yugabyte.com/D33200
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Jira Link: DB-10208
Description
Problem
74064331f0 (tag: 2.21.0.0-b286) [#20003] YSQL: Fix BNL IN array type derivation
. The test case hits the crash fixed by this commit.problem in alloc set CacheMemoryContext...
warnings.Backtrace
Test Case
CREATE TABLE public.c (
pk integer NOT NULL,
col_int_nokey integer,
col_int_key integer,
col_varchar_key character varying(1),
col_varchar_nokey character varying(1),
CONSTRAINT c_pkey PRIMARY KEY(pk ASC)
);
CREATE TABLE public.cc (
pk integer NOT NULL,
col_int_nokey integer,
col_int_key integer,
col_varchar_key character varying(1),
col_varchar_nokey character varying(1),
CONSTRAINT cc_pkey PRIMARY KEY(pk ASC)
);
COPY public.c (pk, col_int_nokey, col_int_key, col_varchar_key, col_varchar_nokey) FROM stdin;
1 2 4 v v
2 150 62 v v
3 \N 7 c c
4 2 1 \N \N
5 5 0 x x
6 3 7 i i
7 1 7 e e
8 4 1 p p
9 \N 7 s s
10 2 1 j j
11 6 5 z z
12 6 2 c c
13 8 0 a a
14 2 1 q q
15 6 8 y y
16 8 1 \N \N
17 3 1 r r
18 3 9 v v
19 9 1 \N \N
20 6 5 r r
.
COPY public.cc (pk, col_int_nokey, col_int_key, col_varchar_key, col_varchar_nokey) FROM stdin;
10 \N 8 x x
11 8 7 d d
12 1 1 r r
13 9 7 f f
14 4 9 y y
15 3 \N u u
16 2 1 m m
17 \N 9 \N \N
18 2 2 o o
19 \N 9 w w
20 6 2 m m
21 7 4 q q
22 2 0 \N \N
23 5 4 d d
24 7 8 g g
25 6 \N x x
26 6 \N f f
27 2 0 p p
28 9 \N j j
29 6 8 c c
.
CREATE INDEX c_varchar_key ON public.c (col_varchar_key ASC, col_int_key ASC);
CREATE INDEX cc_varchar_key ON public.cc (col_varchar_key ASC, col_int_key ASC);
/+ Set(enable_hashjoin off) Set(enable_mergejoin off) Set(enable_material off) /
SELECT
FROM
C AS table1
JOIN (
SELECT
SUBQUERY2_t2.
FROM
C AS SUBQUERY2_t2
JOIN C AS SUBQUERY2_t3 ON (
SUBQUERY2_t3.col_varchar_nokey = SUBQUERY2_t2.col_varchar_key
)
WHERE
SUBQUERY2_t3.pk <> 43
)
AS table2 ON (
table2.col_varchar_key = table1.col_varchar_key
)
JOIN (
SELECT
SUBQUERY3_t1.
FROM
CC AS SUBQUERY3_t1
JOIN CC AS SUBQUERY3_t2 ON (
SUBQUERY3_t2.col_int_nokey = SUBQUERY3_t1.col_int_key
)
WHERE
SUBQUERY3_t1.col_varchar_key != SUBQUERY3_t2.col_varchar_key
)
AS table3 ON (
table3.col_varchar_key = table2.col_varchar_nokey
)
WHERE
EXISTS (
SELECT
MIN (
SUBQUERY4_t2.col_varchar_key
)
FROM
C AS SUBQUERY4_t1
JOIN C AS SUBQUERY4_t2 ON (
SUBQUERY4_t2.col_varchar_key = SUBQUERY4_t1.col_varchar_key
)
WHERE
SUBQUERY4_t2.pk <= table2.col_int_nokey
AND
SUBQUERY4_t2.col_int_key < table1.pk
)
OR
table3.col_varchar_key >= table1.col_varchar_key
;
The text was updated successfully, but these errors were encountered: