RE: BUG #15460: Error while creating index or constraint

From: Paul van der Linden <paul(dot)vanderlinden(at)mapcreator(dot)eu>
To: Peter Geoghegan <pg(at)bowt(dot)ie>
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 13:44:38
Message-ID: AM0PR0402MB342585A7F79445A178A30AAAECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Amcheck is still running.
Trace_sort is attached

-----Original Message-----
From: Peter Geoghegan <pg(at)bowt(dot)ie>
Sent: maandag 29 oktober 2018 14:26
To: Paul van der Linden <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

On Mon, Oct 29, 2018 at 1:01 PM Paul van der Linden <paul(dot)vanderlinden(at)mapcreator(dot)eu> wrote:
>
> Well I also saw it on uuids and possibly enum.
> One of the tables is a materialized view with 550161114 records consisting of 2 uuid-colums and 2 enum columns.
> Total size is 34 GB...

Another thing that could be helpful is if you "set trace_sort = on"
within your session/pgAdmin, and showed us log output from the start of the failing CREATE INDEX to the point that it fails. You may or may not want to "set client_min_messages = LOG" while you're at it, since that will send LOG output to the client, which may be more convenient.

Thanks
--
Peter Geoghegan

Attachment Content-Type Size
trace_sort.log application/octet-stream 17.6 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2018-10-29 14:11:08 Re: BUG #15460: Error while creating index or constraint
Previous Message Peter Geoghegan 2018-10-29 13:26:23 Re: BUG #15460: Error while creating index or constraint