Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)

From: Andres Freund <andres(at)anarazel(dot)de>
To: Peter Geoghegan <pg(at)bowt(dot)ie>,Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>,Prabhat Sahu <prabhat(dot)sahu(at)enterprisedb(dot)com>,Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>,Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>,Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>,Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>,Heikki Linnakangas <hlinnaka(at)iki(dot)fi>,Pg Hackers <pgsql-hackers(at)postgresql(dot)org>,Corey Huinker <corey(dot)huinker(at)gmail(dot)com>
Subject: Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)
Date: 2018-03-08 01:42:10
Message-ID: 6B6AC6DC-B2D1-4233-8220-2FC147D8C3E8@anarazel.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On March 7, 2018 5:40:18 PM PST, Peter Geoghegan <pg(at)bowt(dot)ie> wrote:
>On Wed, Mar 7, 2018 at 5:16 PM, Tomas Vondra
><tomas(dot)vondra(at)2ndquadrant(dot)com> wrote:
>> FWIW that's usually written to the system log. Does dmesg say
>something
>> about the kill?
>
>While it would be nice to confirm that it was indeed the OOM killer,
>either way the crash happened because SIGKILL was sent to a parallel
>worker. There is no reason to suspect a bug.

Not impossible there's a leak somewhere though.

Andres
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Craig Ringer 2018-03-08 01:48:50 Re: Two-phase update of restart_lsn in LogicalConfirmReceivedLocation
Previous Message Peter Geoghegan 2018-03-08 01:40:18 Re: [HACKERS] Parallel tuplesort (for parallel B-Tree index creation)