Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n6bYD-0004w8-8V for pgsql-bugs@arkaria.postgresql.org; Sun, 09 Jan 2022 17:00:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1n6bYB-0006SF-Px for pgsql-bugs@arkaria.postgresql.org; Sun, 09 Jan 2022 17:00:11 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1n6bYB-0006S6-FB for pgsql-bugs@lists.postgresql.org; Sun, 09 Jan 2022 17:00:11 +0000 Received: from mail-lf1-x133.google.com ([2a00:1450:4864:20::133]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1n6bY5-0003t0-SO for pgsql-bugs@lists.postgresql.org; Sun, 09 Jan 2022 17:00:10 +0000 Received: by mail-lf1-x133.google.com with SMTP id g11so36061899lfu.2 for ; Sun, 09 Jan 2022 09:00:05 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-transfer-encoding:content-language; bh=0PHxGP392J62TZWD80n9Ob1uzIziFaEOxDg2YKQoi88=; b=HK234emLCI61RNNme/ofaUMudHPdNfqpU6aZeE8pl19AiVHehajS1oJE7e+SElunK1 HnHUEf7tF09rucI3O15uE61ZU4Kl8BAmHhJ3MJpxdr7jiZctVdLFX9egwcv+HUOtDNkm 6liaNCxnrNeIlsVhn20PgHZV34uO/xTEUmaI2Ah5K2SQs2miPtdIa3g4hwok8o00hzoY GkG2U3NnwhYnnnp7dmflTKJBrizxDBzINzQre+BAehOr23DuoBP/vqyGnLqwpDlvE5Eu B5zuXV/kqwvS83+G0vuDpzMqZuu560Rmv4jivLnJ69K0Y98Ueri0NoJB5/s4Z1nOBgHM onFw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=0PHxGP392J62TZWD80n9Ob1uzIziFaEOxDg2YKQoi88=; b=FxouA5K8xjoYaa6YDaryikJVQTxrtfcNoT+vh6vRY188+GvjrqDhO1stPioPRoiQyO nTlXLvRwpK5w0rQAYcayhb8B6BxnSTLJxEBzA6OAP++9TQ4fQ9LuIhWP1t8YhhmCO0Zh 2TNpXI2VDNi8cn5RpLCFNO9QOUd5Q9pXQ1E9ym5mhZQU62eAvvL5JxkFc5ebNhPbNN61 bbXn+D7OCfErSI9PGO+ZrxPew1P2Dka/MigbAmj2TWnaS8o6J2wnN/HVI5Rmv3ldnLZx /4ptoMlSy/Zd6OvwaZJMEbkyn71Ck3Af3CbtB3sTCWV+f6v61dytQILro7lHE/th3Dne WmOw== X-Gm-Message-State: AOAM530b93923ljzWKoOcjO0HY7gYD/t166CF/I/VT1qbvF1p8BmyZFX cAZug6VxOIoxukBhvR91Ovk= X-Google-Smtp-Source: ABdhPJz8HwsStSTKA+c42J4N/4/xk1ZvUi3wNLx5Qkoi+ieQpQeneHveFgufLYK3ScQ2fnxT3rlW4w== X-Received: by 2002:a05:6512:10d0:: with SMTP id k16mr65227366lfg.97.1641747604231; Sun, 09 Jan 2022 09:00:04 -0800 (PST) Received: from [1.0.0.7] ([178.155.6.84]) by smtp.gmail.com with ESMTPSA id z25sm695195lfq.20.2022.01.09.09.00.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 09 Jan 2022 09:00:03 -0800 (PST) Subject: Re: BUG #17116: Assert failed in SerialSetActiveSerXmin() on commit of parallelized serializable transaction To: Thomas Munro Cc: PostgreSQL mailing lists , heikki.linnakangas@iki.fi, Kevin Grittner References: <17116-d6ca217acc180e30@postgresql.org> <66a6851c-e213-b31a-c8e6-789ab06e17f1@gmail.com> From: Alexander Lakhin Message-ID: <09825f99-97e3-daa1-3d84-05d7263da947@gmail.com> Date: Sun, 9 Jan 2022 20:00:00 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Thomas, 30.07.2021 08:48, Thomas Munro wrote: >>>> (Except for read-only-anomaly-3, that causes another >>>> assertion fail but I believe that it's not related to the initial issue >>>> and deserves another bug report.) > The problem is that if we don't take the fast exit here: You wouldn't mind if I file a separate bug report regarding the last problem (not related to the initial bug report)? Now I can propose a minimal reproduction for it, that can ease testing and choosing the most appropriate fix. As to v4-0001-Fix-assert-failures-in-parallel-SERIALIZABLE-READ.patch you posted before, I believe it fixes the issues as expected and may be committed at least to allow for advanced testing. Best regards, Alexander