RE: BUG #15460: Error while creating index or constraint
От | Paul van der Linden |
---|---|
Тема | RE: BUG #15460: Error while creating index or constraint |
Дата | |
Msg-id | AM0PR0402MB342585A7F79445A178A30AAAECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: BUG #15460: Error while creating index or constraint (Peter Geoghegan <pg@bowt.ie>) |
Ответы |
Re: BUG #15460: Error while creating index or constraint
|
Список | pgsql-bugs |
Amcheck is still running. Trace_sort is attached -----Original Message----- From: Peter Geoghegan <pg@bowt.ie> Sent: maandag 29 oktober 2018 14:26 To: Paul van der Linden <paul.vanderlinden@mapcreator.eu> Cc: PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>; Heikki Linnakangas <hlinnaka@iki.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.vanderlinden@mapcreator.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 theclient, which may be more convenient. Thanks -- Peter Geoghegan
Вложения
В списке pgsql-bugs по дате отправления: