| 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 13:26:23 |
| Message-ID: | CAH2-WznL_9_Xx6bL9_HfC7McDKEjeF7MUDFKScJpxjH7CABhtw@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul van der Linden | 2018-10-29 13:44:38 | RE: BUG #15460: Error while creating index or constraint |
| Previous Message | Peter Geoghegan | 2018-10-29 13:04:58 | Re: BUG #15460: Error while creating index or constraint |