From: | Peter Geoghegan <pg(at)bowt(dot)ie> |
---|---|
To: | paul(dot)vanderlinden(at)mapcreator(dot)eu |
Cc: | PostgreSQL mailing lists <pgsql-bugs(at)lists(dot)postgresql(dot)org>, Heikki Linnakangas <hlinnaka(at)iki(dot)fi> |
Subject: | Re: BUG #15460: Error while creating index or constraint |
Date: | 2018-10-29 12:53:28 |
Message-ID: | CAH2-Wz=1LHGGGch1CW+68+Np4zva5wJ9Vh50SoPfz_rX-pGoFw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Mon, Oct 29, 2018 at 12:45 PM Paul van der Linden
<paul(dot)vanderlinden(at)mapcreator(dot)eu> wrote:
> It happens with both unique and non-unique index.
> When I disable virusscanner I also get the error, but settin g the max_parallel_workers to 0 does let me create the index
Thanks for trying that out. This confirms that parallel CREATE INDEX
is involved.
Is it possible for you to provide me with a dump of the data, or a
minimal test case? You can provided it to me off-list if that's
easier, possibly using Google drive or something. I realize that the
amount of data involved here isn't trivial, so this may be difficult.
I'm a little suspicious of the fact that your table is probably
aligned to certain boundaries, since it consists only of
integers/bigints. Maybe that's just a coincidence, though.
Thanks
--
Peter Geoghegan
From | Date | Subject | |
---|---|---|---|
Next Message | Paul van der Linden | 2018-10-29 13:01:15 | RE: BUG #15460: Error while creating index or constraint |
Previous Message | Paul van der Linden | 2018-10-29 12:45:10 | RE: BUG #15460: Error while creating index or constraint |