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 1pcjph-0006RZ-2P for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Mar 2023 09:23:37 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pcjpf-0005xY-Q2 for pgsql-hackers@arkaria.postgresql.org; Thu, 16 Mar 2023 09:23:35 +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 1pcjpf-0005xM-Fw for pgsql-hackers@lists.postgresql.org; Thu, 16 Mar 2023 09:23:35 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1pcjpd-0007sa-2g for pgsql-hackers@lists.postgresql.org; Thu, 16 Mar 2023 09:23:34 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-17ac5ee3f9cso1389647fac.12 for ; Thu, 16 Mar 2023 02:23:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; t=1678958612; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=KanPA7dJEhbzn1PkCU6y7llfGsusD9Qj+dK25eFRRPc=; b=Ogs3m1nsG6jA7J/3xkjb9AKGUu7SbX3FyTjSACyp975zBpnes0UTKoFnFmiuDhywLW UcyQ5FqCW+zi7YSrfulVGZ6l0igjvcIBnb9ogBGpqTLtSj+vgjQAR60aT/3eI1gSyg8R 3bbrdVWNW4Uqi6nFI/cAjpT9C9eMJYofTZbwEHtsOGJ7UqLOhRbq0J1aSm3hh4TP5Tz8 JxCS4okFuHnT91XUaZMtfSa3W983yfpB34WK5xUuRo3+L6NlXhocqDoNeMMoCctCtYXH tillNgHC+qEc2iqw3iKLdEW7SZqsmTMY1TPuy+XgMNAviIaDD9xmk4z8yMnMMAbu5/DK P7nA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678958612; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=KanPA7dJEhbzn1PkCU6y7llfGsusD9Qj+dK25eFRRPc=; b=nNeuu+6wsgF7oKTR3DOIRbU9sRxFPk5fxK0YIJkbvwhLxOAkgjORuU+gWty7LpPQ7K GcI2LMSiuz3oF6ZNcV7uWzR6A8LMqIvR7UwxMRdXiMEzJJ4/FkY3GwgFZZXENxfvQz+P TLFlqRgmDRl5uTlPwjrQ5e1Ux7dMXgczJLoHPm4yIsFZHCcmnwOiWUs5apo23D3wAA4s gU0aCgm/bMfRtnuu/we3IsB0LFh2FQcj1DAKBB8vNwCZSi/1xmCvxhYzYWwPaa0ppKHr YToey5pqOvVMIE/ibXyhiHwjqVFRD3OLQmnfgP6UCEwWv3c2EfvwqcexOS97COK36Fzq 0QJw== X-Gm-Message-State: AO0yUKUgs7xdffRfYrCFukhGxPKr97CJ8ITnFvegGDhO5hf4SuOnoS9F BS6s9WZxTZtOMar1LPyuOlHJeSUznAPPKA9h77zgsXLW7/9Tlg== X-Google-Smtp-Source: AK7set9ky4K042P5q9ZnuQ71eCDGekdjCPDQ2gbOzpEK7YckwGQrD4mLFlGwvmLB/w7iEN1p3lZRaFk+1BlSpuxmuFA= X-Received: by 2002:a05:6870:1218:b0:177:96d4:bf93 with SMTP id 24-20020a056870121800b0017796d4bf93mr6975175oan.2.1678958612064; Thu, 16 Mar 2023 02:23:32 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Amit Kapila Date: Thu, 16 Mar 2023 14:53:19 +0530 Message-ID: Subject: Re: Dropped and generated columns might cause wrong data on subs when REPLICA IDENTITY FULL To: =?UTF-8?B?w5ZuZGVyIEthbGFjxLE=?= Cc: "shiy.fnst@fujitsu.com" , PostgreSQL Hackers Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Mon, Mar 13, 2023 at 6:26=E2=80=AFPM =C3=96nder Kalac=C4=B1 wrote: > > Attaching v2 > Can we change the comment to: "Ignore dropped and generated columns as the publisher doesn't send those."? After your change, att =3D TupleDescAttr(slot1->tts_tupleDescriptor, attrnum); is done twice in the same function. In test cases, let's change the comment to: "The bug was that when the REPLICA IDENTITY FULL is used with dropped or generated columns, we fail to apply updates and deletes.". Also, I think we don't need to provide the email link as anyway commit message will have a link to the discussion. Did you check this in the back branches? --=20 With Regards, Amit Kapila.