On 2020-Jan-20, Heikki Linnakangas wrote:
> Sorry, forgot all about it. Pushed now.
Thank you!
--
Álvaro Herrerahttps://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
On 17/01/2020 23:35, Alvaro Herrera wrote:
On 2019-Aug-28, Heikki Linnakangas wrote:
I bumped into a little bug in BRIN, while hacking on something unrelated.
This causes a segfault, or an assertion failure if assertions are enabled:
Heikki, I just noticed that you haven't pushed this bugfix.
On 2019-Aug-28, Heikki Linnakangas wrote:
> I bumped into a little bug in BRIN, while hacking on something unrelated.
> This causes a segfault, or an assertion failure if assertions are enabled:
Heikki, I just noticed that you haven't pushed this bugfix. Would you
like me to? (If I don't hear f
Heikki Linnakangas writes:
> I bumped into a little bug in BRIN, while hacking on something
> unrelated. This causes a segfault, or an assertion failure if assertions
> are enabled:
Good catch.
> Fix attached.
Hm, I don't particularly care for directly comparing Datum values
like that. We do
Thank you for your fix.
> This assumes that the merge function returns a newly-palloc'd value.
> That's a shaky assumption; if one of the arguments is an empty range,
> range_merge() returns the other argument, rather than a newly
> constructed value. And surely we can't assume assume that for
> u
I bumped into a little bug in BRIN, while hacking on something
unrelated. This causes a segfault, or an assertion failure if assertions
are enabled:
CREATE TABLE brintest (n numrange);
CREATE INDEX brinidx ON brintest USING brin (n);
INSERT INTO brintest VALUES ('empty');
INSERT INTO brintest
