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 1nUvaj-0000jv-Uw for pgsql-committers@arkaria.postgresql.org; Thu, 17 Mar 2022 19:15:21 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nUvai-0001VD-QZ for pgsql-committers@arkaria.postgresql.org; Thu, 17 Mar 2022 19:15:20 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nUvai-0001Ud-JE for pgsql-committers@lists.postgresql.org; Thu, 17 Mar 2022 19:15:20 +0000 Received: from mail-lj1-x229.google.com ([2a00:1450:4864:20::229]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nUvae-0004FF-3P for pgsql-committers@lists.postgresql.org; Thu, 17 Mar 2022 19:15:20 +0000 Received: by mail-lj1-x229.google.com with SMTP id g24so7327328lja.7 for ; Thu, 17 Mar 2022 12:15:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=vvR7o5l5eUiU/p1mAYvinC9YCs59bvVu95cc13aBOIY=; b=fzMUD3vwu21vz+1VHg6s4GyYqwuI+2R0hL3pgNiy/q70mCpGkS/5yc4ZvssSjRdKFg g1caozkKXEGyKerZ8KAK05BEPxq1C6BJlL/NCsbOhm9csZyWEhx/8cicbOBtXoNuexqf MpXcXt2sgLeoSYfBy4dAmFyP/L5eniPp89leP5rOT0qZFZV6O/kw9KpMcSMXtOL7v1Ll 1dQZIYJaxkQ0/bLnkvmzIQ6eMcBeQfm5qTjRJCjcfjLxiNvmmQ6GO1hDPWomm8TCJdDs gcrVD+DUkyxpwPdYhAN2JYwYwHqXpcaTGDn4iem+Jusct0q2nlFz4pAo0CPNhDxLWMdz xcKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=vvR7o5l5eUiU/p1mAYvinC9YCs59bvVu95cc13aBOIY=; b=Ej62XuIsiiaEaaT1JRAutIb8LoZQYNi9WrUMU/JwwSidG4nptSIyZsrPdapqSqfaJO J12jol6KZVzXJFkE9zKu/wmcI1n4bfGSmNd+lqYeq2+Lg5WxTDRLNozjL3BabqjR4fuG CxBIyhgvRt7JVNJU8jOXceR1t3ZNnqCyUGC3UFEwRrC0jaD+RWINmFk5FCY5pyVWLi3p Ero9c6G+46wVe+AWmEa6cvSAZiWNtU9Gvx65UC9kH9To5Ai42RugT6pis24jvjfSaTkO 4JShgsjHdTjSv/zREtUjhD/WpvsZ/c1lftmYjnlLTkSsn0CLMeUjR0PhNvoTnQp3I3AD dhdg== X-Gm-Message-State: AOAM530tzakLOHsAaHgJKMg4yaeq7AJjJaZdgDegGpAXPBlPbqqENSdQ lKwbpkhRS9YccbOAlBNnITgXft85vbkfVrl8Hu0YLHpq7Ue3wd2rp56NKydgwzWnUIPeZCtP7eL 8zb8MpsQU3WrxwP3UCUjRpwbwShNLKIFVobvVye4PnVLZA3l9TY6cP/Ex6QbjMKYJ/sOYPJAtbV PuB0Uj9Ue/T5jqI/KbAk54/4V/IgxzJ2oQqBSFaPT/q5FZrVZcWKk2wQfTqjJhFS4BGHaSEcw= X-Google-Smtp-Source: ABdhPJylzUw1udDy2qAPjjevg+CJep2uJOx/9EDTTnJaSSEurvIU8+i4RYW+ioV+ttimA1ZjKx1NHA== X-Received: by 2002:a2e:9bc6:0:b0:246:440d:b273 with SMTP id w6-20020a2e9bc6000000b00246440db273mr3811692ljj.121.1647544514910; Thu, 17 Mar 2022 12:15:14 -0700 (PDT) Received: from [10.137.0.17] (37-247-27-82.customers.ownit.se. [37.247.27.82]) by smtp.gmail.com with ESMTPSA id a1-20020a056512390100b004483b717210sm512268lfu.79.2022.03.17.12.15.14 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 17 Mar 2022 12:15:14 -0700 (PDT) Message-ID: Date: Thu, 17 Mar 2022 20:15:13 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.6.2 Subject: Re: pgsql: Fix row filters with multiple publications Content-Language: en-US To: Tomas Vondra , pgsql-committers@lists.postgresql.org References: From: Tomas Vondra In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk Hmm, this seems to have failed on wrasse [1], due to a timeout when waiting for tablesync to complete: 2022-03-17 17:39:28.247 CET [19962:1] LOG: logical replication table synchronization worker for subscription "sub2", table "tab1" has started 2022-03-17 17:39:28.258 CET [19964:1] LOG: logical replication table synchronization worker for subscription "sub2", table "tab4" has started In the previous runs this completed pretty much immediately (less than a second), but this time the workers got stuck, so the script keeps looping on the $synced_query. There's nothing in the log, so either it's some sort of lock wait or infinite loop. However, this fails in 013_partition.sql, which was not modified in this commit. And there have been multiple successful runs since it was modified (in c91f71b9dc). So it's not clear if this is a pre-existing issue and we just happened to hit it now, or maybe it's introduced by either c91f71b9dc or 5a07966225. But neither of these commits touched tablesync at all, so I'm puzzled how could it happen. regards [1] https://buildfarm.postgresql.org/cgi-bin/show_log.pl?nm=wrasse&dt=2022-03-17%2016%3A08%3A19 -- Tomas Vondra EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company