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 15:17:58
Message-ID: AM0PR0402MB3425CE2317FBD9013CCB865FECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Hm, the log_line_prefix didn't change a lot in the logs...
And what's worse (but completely unrelated): the performance benefits of upgrading to pg11 don't work for me (having a big number of heavy geocalculations unioned all into one select still doesn't use more than one worker/core...)

-----Original Message-----
From: Peter Geoghegan <pg(at)bowt(dot)ie>
Sent: maandag 29 oktober 2018 15:31
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 2:28 PM Paul van der Linden <paul(dot)vanderlinden(at)mapcreator(dot)eu> wrote:
>
> I do see some files now (0.0, 1.0 and 2.0) in that directory.
> Not able to restart postgres at the moment because it's also running some other stuff...

No need to restart. Just call pg_reload_conf() as a superuser, once postgresql.conf has the change. That won't be disruptive.

--
Peter Geoghegan

Attachment Content-Type Size
trace_sort2.log application/octet-stream 17.9 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Peter Geoghegan 2018-10-29 15:24:16 Re: BUG #15460: Error while creating index or constraint
Previous Message Peter Geoghegan 2018-10-29 15:15:03 Re: BUG #15460: Error while creating index or constraint