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 1ru7eW-002fhO-Mf for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 09:20:29 +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 1ru7eV-002Etz-U1 for pgsql-general@arkaria.postgresql.org; Tue, 09 Apr 2024 09:20:27 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1ru7eV-002Etr-JL for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 09:20:27 +0000 Received: from mail-ed1-x52b.google.com ([2a00:1450:4864:20::52b]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1ru7eT-001ydg-57 for pgsql-general@lists.postgresql.org; Tue, 09 Apr 2024 09:20:26 +0000 Received: by mail-ed1-x52b.google.com with SMTP id 4fb4d7f45d1cf-56e448d6f9cso1466754a12.0 for ; Tue, 09 Apr 2024 02:20:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712654423; x=1713259223; darn=lists.postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=1ikjhemMOs8j7qI3xEUtalSHs2V74YteHHUkwXxZDME=; b=O78pJUncG83kCXkHKsWGjSbIAKCtgnbnbGteQyUm+jIlO2VBaV0/ioWOkXBU8NWbX3 liKOUQ+9+v0rYnxIuFSOhwUT5d2vO4ND3nSeraMan/DX8wQowx0JKsmF52m/fLY8Qcxw D25MriSdtVSslh/iIOG9mIIUtUI0+yLN6fVeAn9hcqytl4lO3LFGaM5VlfqrRgDC4wpM dpq3hLbnDC9u/n0OH632p7LZNAB0K517MImYJmgNyE7P61RLvKGLiMxpDxrf2syi8PIF l0alBMIsFBvaG6jwVICkPKh5ZOPcUmU6kF12UMs8y7vJjTC1xcnr1eEj/KRaYDez2L91 xdCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712654423; x=1713259223; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=1ikjhemMOs8j7qI3xEUtalSHs2V74YteHHUkwXxZDME=; b=ktNS6HBiRBynkbD0KfjFZaxAt12lrU8CNUID8X2Fhsr2U5p12HMqnoe4F9c6V8/3RP Oj02yhC+e1vI4uuq5mB24cZpHdzVYo5RMqAqrxbbq4I6wHImveNMc4kmBEFb1Yx/stuN ++BaDeGLb98nWFu8nyI/Ht7oKqn6wPDVkgakBt3c5A/YGwURl86rulEfNwgcYbwsiCr1 oDYHPowOSTb42kAPtNPRCDtgf/tYyvp1V/PcqdZAOXfiIszHLd/wFaNJO4P5qAO0g0X3 m8tcDD3D/T2yp+vDZhrd3zsz87U4JG1kGCn6lw9OWBmGkBUOvJBn1CSC+tlfZ1mDP5NR iAqA== X-Gm-Message-State: AOJu0YxE+gF0MTFeJNVx5ELao2ekNtNpF8Tr5GSqum9RKS4GxAR0AqCX U0VKf+8h672r/s2EdkVqM4LgZ8ukHRfRC20nLPFjh5ht5oDYFFGDwmpKligHTtE6YeACIYAb0FZ j0ulHxeeM5Br40GaMlNaLL+M3PPpKo5x35YY= X-Google-Smtp-Source: AGHT+IF1jVHIjH6yMG9fy3yGvAs85RttmFbeG5pXRADFkSEAjiEA0F9ZvhUzC4IUEJ3qvcd+YC5IrUsFi6vtrOfh5l0= X-Received: by 2002:a17:907:7e90:b0:a51:ab69:dc50 with SMTP id qb16-20020a1709077e9000b00a51ab69dc50mr8721206ejc.15.1712654423019; Tue, 09 Apr 2024 02:20:23 -0700 (PDT) MIME-Version: 1.0 From: Arvind Raghuwanshi Date: Tue, 9 Apr 2024 14:50:10 +0530 Message-ID: Subject: Regarding: Replication of TRUNCATE commands is not working To: pgsql-general@lists.postgresql.org Content-Type: multipart/alternative; boundary="00000000000081da960615a66ee5" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000081da960615a66ee5 Content-Type: text/plain; charset="UTF-8" Hi, I have tried to run the TRUNCATE command and found out that it's not getting replicated using logical replication for pgsql. I have also checked the schema change using pg_dump command but the schema change also not getting detected for TRUNCATE command. However on pgsql logical replication doc page[1] , it's mentioned that Replication of TRUNCATE commands is supported. [1] PostgreSQL: Documentation: 16: 31.6. Restrictions Any idea how we can solve this? Thanks Arvind --00000000000081da960615a66ee5 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi,I have tried to run the TRUNCATE command=C2=A0 and found out that it's= not getting replicated using logical replication for pgsql.
I ha= ve also checked the schema change using pg_dump command but the schema chan= ge also not getting detected for TRUNCATE command.

However on pgsql logical replication doc page[1] , it's mentioned that= =C2=A0Replication of TRUNCATE commands is supported.

[1]=C2=A0PostgreSQL: Documentation: 16: 31.6.=C2=A0Restri= ctions

Any idea how we can solve=C2=A0this= ?

Thanks
Arvind
<= /div> --00000000000081da960615a66ee5--