Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1inoWk-0004LT-AO for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Jan 2020 18:51:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1inoWi-000886-Lh for pgsql-hackers@arkaria.postgresql.org; Sat, 04 Jan 2020 18:51:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1inoWi-00086g-4o for pgsql-hackers@lists.postgresql.org; Sat, 04 Jan 2020 18:51:56 +0000 Received: from mail-pl1-x643.google.com ([2607:f8b0:4864:20::643]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1inoWf-0008IC-HI for pgsql-hackers@lists.postgresql.org; Sat, 04 Jan 2020 18:51:55 +0000 Received: by mail-pl1-x643.google.com with SMTP id y8so20229968pll.13 for ; Sat, 04 Jan 2020 10:51:53 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=leadboat.com; s=google; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Sh2pq/SJaCmhEgp556oZGRnhyPN44HaTTZCZR+RvfqQ=; b=GW1xUDBh52Nw3XB94bxyIxKGeiwa62bmK1NfKfNbR6/GaWNeYt0qlg+KfNdf4FlVdM x2ar7cNDQNKSXWSv/ys5tLMeC0nEEns2NF/QkHJcWJMNSPX8LqAr0ie4nD54DZFGwoyu 0WNo0R5pT0/x4QAHnzNdJpTYI82u7NCJjrnrE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Sh2pq/SJaCmhEgp556oZGRnhyPN44HaTTZCZR+RvfqQ=; b=jjHo4qeROQypINDQZLhlwoO5w3/N9fltRfdujW+6xzMfG//LhnBHiZvgDkXsAsfhgO vcEal5G18wZlg+rX6UzNNLKomVGraXWGoYnZ0wdKF/E3zGPRqPUKA8dIIDvA3kUP2peI fD9URaFt6QfIpcvEAlv+rQPCw/yIgXR+h37U2rICuNmu35lwf+mQeWlPdkWvO7Rofzzv KJzW3J2/zw6odRRG8tcJ+xSlXipLpG9y+DhaMTj2ClV6eTePMiA5XLkydhu7I6/xMSYe GOmZk/drbbukTvW/kYg5RDL4TJUs9t2Mnp89u16j5wdFmRVAxRzfVSGzLQOZHbL/Cj5+ gpzg== X-Gm-Message-State: APjAAAXwaw/FzKskLXyO1cFTPmaZWj/dz93ojDlCdCchqVTuq+Fh5iUC bPy4Y4JJNn+XZMspxaUyeVkPVA== X-Google-Smtp-Source: APXvYqz2rjPOgMiJT+Xyk/PkHZCxJ5OlNUsHbaCs7SbN34/8l6lYKDxlIP+NSH83rxQUW+iyN17lMw== X-Received: by 2002:a17:902:760e:: with SMTP id k14mr99679571pll.238.1578163911594; Sat, 04 Jan 2020 10:51:51 -0800 (PST) Received: from rfd.leadboat.com (108-233-125-46.lightspeed.sntcca.sbcglobal.net. [108.233.125.46]) by smtp.gmail.com with ESMTPSA id w38sm69679909pgk.45.2020.01.04.10.51.49 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 04 Jan 2020 10:51:50 -0800 (PST) Date: Sat, 4 Jan 2020 10:51:48 -0800 From: Noah Misch To: Amit Kapila , Amit Khandekar Cc: Alvaro Herrera from 2ndQuadrant , Andres Freund , Juan =?iso-8859-1?Q?Jos=E9_Santamar=EDa?= Flecha , PostgreSQL Hackers , Robert Haas , Thomas Munro , Tom Lane , Tomas Vondra Subject: Re: logical decoding : exceeded maxAllocatedDescs for .spill files Message-ID: <20200104185148.GA2270238@rfd.leadboat.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Fri, Jan 03, 2020 at 02:20:09PM +0530, Amit Khandekar wrote: > On Fri, 3 Jan 2020 at 10:19, Amit Kapila wrote: > > On Fri, Jan 3, 2020 at 8:29 AM Amit Kapila wrote: > >> I see one failure in REL_10_STABLE [1] which seems to be due to this commit: > > > > I tried this test on my CentOs and Power8 machine more than 50 times, but couldn't reproduce it. So, adding Noah to see if he can try this test [1] on his machine (tern) and get stack track or some other information? > > > > [1] - make -C src/test/recovery/ check PROVE_TESTS=t/006_logical_decoding.pl > > I also tested multiple times using PG 10 branch; also tried to inject > an error so that PG_CATCH related code also gets covered, but > unfortunately didn't get the crash on my machine. I guess, we will > have to somehow get the stacktrace. I have buildfarm member tern running this test in a loop. In the 290 iterations so far, it hasn't failed. I've leave it running for another week or so. The buildfarm client can capture stack traces, but it currently doesn't do so for TAP test suites (search the client code for get_stack_trace). If someone feels like writing a fix for that, it would be a nice improvement. Perhaps, rather than having the client code know all the locations where core files might appear, failed runs should walk the test directory tree for core files?