pg.ddx.io  pgsql-bugs@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Tom Lane <tgl@sss.pgh.pa.us>
To: Peter Geoghegan <pg@bowt.ie>
Cc: paul.vanderlinden@mapcreator.eu, PostgreSQL mailing lists <pgsql-bugs@lists.postgresql.org>
Cc: Heikki Linnakangas <hlinnaka@iki.fi>
Subject: Re: BUG #15460: Error while creating index or constraint
Date: Mon, 29 Oct 2018 12:51:03 -0400
Message-ID: <8330.1540831863@sss.pgh.pa.us> (raw)
In-Reply-To: <CAH2-WzmV0kmPLjV1V+-5pUwDe4zeL14S958xu73knizorVAi4g@mail.gmail.com>
References: <15460-b6db80de822fa0ad@postgresql.org>
	<CAH2-Wzk=pj9SN+=HZCYwAc3WHe+_SErqA3xoLxj2y_GwSQ+Dag@mail.gmail.com>
	<CAH2-Wz=iBEtmVLC0RwhTgKAVDG6_jqsdKh=yfcYqtG+ujr9oJQ@mail.gmail.com>
	<AM0PR0402MB34253F2B997E8188C76E7314ECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com>
	<CAH2-Wz=1LHGGGch1CW+68+Np4zva5wJ9Vh50SoPfz_rX-pGoFw@mail.gmail.com>
	<AM0PR0402MB342582385C2659E908900B72ECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com>
	<CAH2-WznL_9_Xx6bL9_HfC7McDKEjeF7MUDFKScJpxjH7CABhtw@mail.gmail.com>
	<AM0PR0402MB342585A7F79445A178A30AAAECF30@AM0PR0402MB3425.eurprd04.prod.outlook.com>
	<27191.1540827070@sss.pgh.pa.us>
	<CAH2-WzmV0kmPLjV1V+-5pUwDe4zeL14S958xu73knizorVAi4g@mail.gmail.com>

Peter Geoghegan <pg@bowt.ie> writes:
> On Mon, Oct 29, 2018 at 3:31 PM Tom Lane <tgl@sss.pgh.pa.us> wrote:
>>> LOG:  performsort of 0 done: CPU: user: 250.03 s, system: 42.66 s, elapsed: 294.35 s
>>> LOG:  parallel external sort of 0 ended, 462886 disk blocks used: CPU: user: 250.03 s, system: 42.66 s, elapsed: 298.95 s
>>> LOG:  begin index sort: unique = f, workMem = 2096128, randomAccess = f
>>> LOG:  performsort of -1 starting: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
>>> LOG:  could not rmdir directory "base/pgsql_tmp/pgsql_tmp5088.0.sharedfileset": Directory not empty
>>> ERROR:  could not determine size of temporary file "0"

>> "performsort of -1"?  Seems a bit suspicious.

> This just refers to the leader Tuplesortstate. It isn't suspicious.
> We follow the convention that worker -1 is the leader within
> tuplesort.c.

Hmm.  But the sort of "0" has already completed, according to the first
couple of log lines I quoted.  Why is something still trying to access
it?  Why is a worker trying to do anything at all with the leader's
Tuplesortstate?

> trace_sort is a developer option, so this seems fine to me.

That's a poor excuse for ignoring the message style guidelines.
There are many reasons why even experts could get confused trying
to follow badly-written messages.

			regards, tom lane




view thread (42+ messages)  latest in thread

Message-ID: <8330.1540831863@sss.pgh.pa.us>
Permalink:  ../8330.1540831863@sss.pgh.pa.us/
Also on:    postgresql.org/message-id/8330.1540831863@sss.pgh.pa.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-bugs@postgresql.org
  Cc: tgl@sss.pgh.pa.us, pg@bowt.ie, pgsql-bugs@lists.postgresql.org, hlinnaka@iki.fi
  Subject: Re: BUG #15460: Error while creating index or constraint
  In-Reply-To: <8330.1540831863@sss.pgh.pa.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox