From: | Victor Yegorov <vyegorov(at)gmail(dot)com> |
---|---|
To: | Justin Pryzby <pryzby(at)telsasoft(dot)com> |
Cc: | PostgreSQL Developers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: Failure to create GiST on ltree column |
Date: | 2020-05-27 19:17:18 |
Message-ID: | CAGnEbohi_U30HH46FsT0tag69HKRvPX4u=EY_i2do2+WRVKvKw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
пн, 25 мая 2020 г. в 18:25, Justin Pryzby <pryzby(at)telsasoft(dot)com>:
> I wonder if/how that fails if you create the index before adding data:
>
> CREATE TABLE test_path(path ltree);
> CREATE INDEX ON test_path USING GIST(path);
> INSERT INTO test_path SELECT * FROM comments.mp_comments;
>
> Does that fail on a particular row ?
>
> How many paths do you have and how long? How big is the table?
>
Yes, it fails.
I got permission and created a partial dump of the data with:
CREATE TABLE lc AS SELECT id, path FROM comments.mp_comments WHERE
length(path::text)>=500;
Attached. It is reproduces the error I get. One needs to create ltree
extension first.
I understand, that issue most likely comes from the length of the ltree
data stored in the columns.
But error is a bit misleading…
--
Victor Yegorov
Attachment | Content-Type | Size |
---|---|---|
lc.pgdump | application/octet-stream | 29.4 KB |
From | Date | Subject | |
---|---|---|---|
Next Message | Peter Eisentraut | 2020-05-27 19:59:59 | Re: New 'pg' consolidated metacommand patch |
Previous Message | Fabien COELHO | 2020-05-27 17:40:27 | future pg+llvm compilation is broken |