BETWEEN SYMMETRIC condition results in "row is too big: ..., maximumsize 8160" - Mailing list pgsql-bugs

From Manuel Rigger
Subject BETWEEN SYMMETRIC condition results in "row is too big: ..., maximumsize 8160"
Date
Msg-id CA+u7OA6zYX7qfkGGDfqeFwuh6HbD4B-0fmOfx13Jm4xsp3s=-Q@mail.gmail.com
Whole thread Raw
Responses Re: BETWEEN SYMMETRIC condition results in "row is too big: ..., maximum size 8160"  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-bugs
Hi everyone,

I noticed that indexes that use nested BETWEEN SYMMETRIC operators
quickly exceed some limit, which is indicated by errors such as
"ERROR:  row is too big: size 8440, maximum size 8160". For example,
consider the following (contrived) index:

CREATE TABLE t0(c0 TEXT);
CREATE INDEX i0 ON t0(c0) WHERE ((FALSE BETWEEN SYMMETRIC TRUE AND
(t0.c0 || t0.c0 IN (t0.c0, t0.c0, '1', t0.c0 || t0.c0, t0.c0 || t0.c0
|| t0.c0))) BETWEEN SYMMETRIC TRUE AND TRUE) BETWEEN SYMMETRIC TRUE
AND TRUE; -- ERROR:  row is too big: size 8440, maximum size 8160

Is this an expected limitation?

Best,
Manuel



pgsql-bugs by date:

Previous
From: raf
Date:
Subject: Re: BUG #15911: Why no Bcrypt in pg_hba.conf?
Next
From: Tom Lane
Date:
Subject: Re: BETWEEN SYMMETRIC condition results in "row is too big: ..., maximum size 8160"