| From: | Siarhei Siniak <siarheisiniak(at)yahoo(dot)com> |
|---|---|
| To: | Daniel Gustafsson <daniel(at)yesql(dot)se> |
| Cc: | "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GiST limits on contrib/cube with dimension > 100? |
| Date: | 2019-06-12 06:30:48 |
| Message-ID: | 1397609375.64903.1560321049004@mail.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Can you point out a failling unit test in the codebase?
P.S sorry for a late reply, has got this message in the spam folder )
Le lundi 10 juin 2019 à 14:57:32 UTC+3, Daniel Gustafsson <daniel(at)yesql(dot)se> a écrit :
> On 9 Jun 2019, at 20:05, Siarhei Siniak <siarheisiniak(at)yahoo(dot)com> wrote:
>
> I've been using cube extension recompiled with
> #define MAX_DIM 256.
>
> But with a version 11.3 I'm getting the following error:
> failed to add item to index page in <index_name>
This sounds like a variant of the issue reported on -bugs in
AM6PR06MB57318C9882C021879DD4101EA3100(at)AM6PR06MB5731(dot)eurprd06(dot)prod(dot)outlook(dot)com
and is also reproducible on HEAD.
cheers ./daniel
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Heikki Linnakangas | 2019-06-12 06:31:39 | Re: pgbench rate limiting changes transaction latency computation |
| Previous Message | Fabien COELHO | 2019-06-12 06:23:33 | Re: pgbench rate limiting changes transaction latency computation |