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 1kpf9J-0004lL-E2 for pgsql-admin@arkaria.postgresql.org; Wed, 16 Dec 2020 22:19:57 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1kpf9I-0008LV-Dx for pgsql-admin@arkaria.postgresql.org; Wed, 16 Dec 2020 22:19:56 +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 1kpf0M-0005cQ-Dg for pgsql-admin@lists.postgresql.org; Wed, 16 Dec 2020 22:10:42 +0000 Received: from mail-pg1-x52d.google.com ([2607:f8b0:4864:20::52d]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1kpf0K-00021L-1w for pgsql-admin@lists.postgresql.org; Wed, 16 Dec 2020 22:10:41 +0000 Received: by mail-pg1-x52d.google.com with SMTP id c22so3176755pgg.13 for ; Wed, 16 Dec 2020 14:10:39 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:from:to:message-id:in-reply-to:references:subject:mime-version; bh=3NgVPl6t7BiNbo+3OTVaxK20VWP5UaxfMBTjq23DwL8=; b=Y8FPUTsEK/zcdOdmPVbfYqweXBigNPD7hPY2ZQ/fgUIC0gbJ0jQxg1uAStK2dCrrc4 tyx5EjvyjXXF/CyllJTZDK1D5Ek0GCI9caMmq0beDJEIWEo2Qz9KlYaaCQVDQAZc08Es hqCFomj6DNHTsgE/d6TN9dC843lbU4lCn325cB92L5ZbxkYefBGn/32Mm97ULaaOLg2H bV3El7DaOuHeYceubZfQHvibEOahjUpKr71W0Fcdw2v+H6zdFsA20kQ8CxQHlOjKG2/W ahFRb+Lt5ebWBGJbyUR6a9qtRAlw4gWaP/InNAkIUIDspiMzHSKrZykC5UHLEb1mng9M YnVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:message-id:in-reply-to:references :subject:mime-version; bh=3NgVPl6t7BiNbo+3OTVaxK20VWP5UaxfMBTjq23DwL8=; b=dNzlhNLhN1otfQUkMKB6JcP8iHDQ5Zy4+bcGQbMrB6O2o5ABCgq5gfTM7rSVnNY0FX wLsBqCvO5ZBBZLfceBO+Wz60DAzGDH8y41NjzSZVsw4QHmmqznDSdi+4Ss6/eTjxGuSt /9i99QUff1bMYCD+yj87QVOC/EIOWSOizfdASWrWj+lI8nYEMhOVVfGfiTp2bVb/Sw/h ZtprQIdo+NnIsAuKUrSxwPe7rgmSlNTT/b2PCn5mWPPlLEC7VT/mDpGoOvEF00exWc8/ V97znDnhNUjikgzloN3ZMzk6fWg3dQaIvYfHr4/XBhh/RnIfuahoFhsYnxbyZwjWXyGh 3/jQ== X-Gm-Message-State: AOAM532ND0Ao5/ZaJrXP2KDqHFwpxKToHIUuILkBXOIOSqqN06qcSpSL hKW6JvgkWvVhu3FgbmMgvCgdfX4oSRy5uA== X-Google-Smtp-Source: ABdhPJzsFbW88tIF3Mneuc/JI5KLtlhm0oTrA55jgQ4HUZwVPPlF/xvc0iJdGR9B2WXoWhkN4TveOw== X-Received: by 2002:a62:c1c4:0:b029:1a7:efe9:163c with SMTP id i187-20020a62c1c40000b02901a7efe9163cmr6703918pfg.47.1608156638383; Wed, 16 Dec 2020 14:10:38 -0800 (PST) Received: from [10.79.14.161] ([192.19.228.250]) by smtp.gmail.com with ESMTPSA id nk11sm2943966pjb.26.2020.12.16.14.10.37 for (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 16 Dec 2020 14:10:37 -0800 (PST) Date: Wed, 16 Dec 2020 15:10:31 -0700 From: Craig Jackson To: Pgsql-admin Message-ID: In-Reply-To: <31314397-9cc1-479f-ab41-b415458a4da7@Spark> References: <31314397-9cc1-479f-ab41-b415458a4da7@Spark> Subject: Errror when trying to create a logical replication slot X-Readdle-Message-ID: c3389938-1a1c-4edb-a573-610e37cb9f2c@Spark MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="5fda85dd_7fdcc233_33b" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --5fda85dd_7fdcc233_33b Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Hi All, We get the following error when trying to test creating a logical replica= tion slot in Postgres version 11.9 >SELECT * =46ROM pg=5Fcreate=5Flogical=5Freplication=5Fslot('regression=5F= slot', 'test=5Fdecoding'); ERROR: cannot create logical replication slot in transaction that has per= formed writes We are running the above command from psql and have tried issuing a rollb= ack prior to running the command but still get the same error. We have the following settings enabled: >show wal=5Flevel; =C2=A0wal=5Flevel ----------- =C2=A0logical >show max=5Freplication=5Fslots; =C2=A0max=5Freplication=5Fslots ----------------------- =C2=A025 Any suggestions on what may be causing the above error are appreciated. Regards, Craig Jackson --5fda85dd_7fdcc233_33b Content-Type: text/html; charset="utf-8" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Hi All,

We get the following error when trying to test creating a logical replica= tion slot in Postgres version 11.9

>SELECT * =46ROM pg=5Fcreate=5Flogical=5Freplication=5Fslot('regressio= n=5Fslot', 'test=5Fdecoding');
ERROR: cannot create logical replication slot in transaction that has per= formed writes

We are running the above command from psql and have tried issuing a rollb= ack prior to running the command but still get the same error.&=23160;
We have the following settings enabled:

>show wal=5Flevel;
&=23160;wal=5Flevel
-----------
&=23160;logical

>show max=5Freplication=5Fslots;
&=23160;max=5Freplication=5Fslots
-----------------------
&=23160;25

Any suggestions on what may be causing the above error are appreciated.&=23= 160;

Regards,


Craig Jackson&=23160;
--5fda85dd_7fdcc233_33b--