Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSffc-00FAbS-Vn for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 16:00:09 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1rSffc-0064Xb-6O for pgsql-bugs@arkaria.postgresql.org; Wed, 24 Jan 2024 16:00:08 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rSffb-0064XT-UF for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 16:00:07 +0000 Received: from mail-lf1-x133.google.com ([2a00:1450:4864:20::133]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rSffY-003Usb-Ae for pgsql-bugs@lists.postgresql.org; Wed, 24 Jan 2024 16:00:07 +0000 Received: by mail-lf1-x133.google.com with SMTP id 2adb3069b0e04-50eabd1c701so6421510e87.3 for ; Wed, 24 Jan 2024 08:00:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1706112003; x=1706716803; darn=lists.postgresql.org; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=nb4Ri8eVXnnNQk27aFgnt7VnImF/IYFDHjOlb4enkH4=; b=i33KgnNZE5MNavaHav9PTB26qwsT8byzCnvgVPQFA5tERhWTqhEgo4ux0fTkDj0VEv 6cFqiMS34yVyKh0qVGXJ+ve3UZH+M3XtCx84qdMC8g5ZKhAfyyTCTBz5zid5HIXiFzjm BXj1QI6NnKSKn9IKzp0p4RXyDx5+SD1KQ4eFiQdsEhDnXEtEFBoIsG/QoRwozCpC/yFw UtxIChCwuetFLYyXRuUdaM07E+ugriJunuByhGfhUWNzyuKJZ9YT0X+1rOLGwiBP+2JU oYS2v5NE0CoLFQ4LJWSGHM47RzqUda0LD5hekoFMNj9/zbQMFDPHATXFCvGFu5U84/sQ Zl5Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1706112003; x=1706716803; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=nb4Ri8eVXnnNQk27aFgnt7VnImF/IYFDHjOlb4enkH4=; b=h9WZXghcXkLM4GgdPy0twzP9DTnYOgfsv0nU1EGFwpUk0CkP1u463nR6qTgIZ1CbCY ySqzRoqMcyWVC6VaVXxPDDCbOX2OWDwrfEyksXf8ndn8NBn2qqGcZA+AfSehZe/OvrGb o63y6oLYLYEQk8DuzNsln+kZO3DDx0wmRBFOqspuKeSqsx2sctcyMTPKaxKms3rnWUFg LOW05AQUTPWEvi/zu+xd1ZfBGaKCFp+pI2+VAftLeRyFXfI0W11pqYgMi/e1Ab60fShM kID80va1FKZf32nEFu3o7IgXzwqI3755j7eYsaei6KvLAIdG76nzfbxg3PpW3E7xAo/S Eh2g== X-Gm-Message-State: AOJu0YwXZDyOXjuBFOl5J1kg8oq8SxGU4Zaq71sKzhBOXzXgGnBamz4s D7O8ahr7jT1vc4xdnY0hwSGZkif3m5CjhY4DuLjSvM671JRWXfp0 X-Google-Smtp-Source: AGHT+IHgNRWoN7So/rHWdLdn5VCJmvdUu7QmLxwDEZTRnFGAjGUV1PVOeVakLmwsDu9Et4yBYOM0SQ== X-Received: by 2002:ac2:47e4:0:b0:510:84b:71c8 with SMTP id b4-20020ac247e4000000b00510084b71c8mr1526934lfp.114.1706112003020; Wed, 24 Jan 2024 08:00:03 -0800 (PST) Received: from [1.0.0.7] ([91.185.77.50]) by smtp.gmail.com with ESMTPSA id be34-20020a056512252200b0050e798ab1b9sm2633387lfb.139.2024.01.24.08.00.02 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 24 Jan 2024 08:00:02 -0800 (PST) Message-ID: <6a921555-8643-4fd8-443e-4471eb5868b4@gmail.com> Date: Wed, 24 Jan 2024 19:00:00 +0300 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.4.2 Subject: Re: BUG #18309: TOASTed entry in pg_subscription provokes an assertion failure Content-Language: en-US To: Daniel Gustafsson , pgsql-bugs@lists.postgresql.org References: <18309-c0bf914950c46692@postgresql.org> From: Alexander Lakhin In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hello Daniel, 24.01.2024 18:24, Daniel Gustafsson wrote: > This seems like a variation of the issue reported in the login event trigger > thread at postgr.es/m/e2a0248e-5f32-af0c-9832-a90d303c2c61@gmail.com Yes, it has the same root cause, but maybe it should be fixed differently. I had also reported: https://www.postgresql.org/message-id/18127-fe54b6a667f29658%40postgresql.org but I'm not sure that all of these issues should be fixed by a single commit. (Given that there are 7c38ef2a5 and 54b208f90 already.) Though maybe I'm wrong here. Best regards, Alexander