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 1stZ1H-00HOsq-GO for pgsql-in-general@arkaria.postgresql.org; Wed, 25 Sep 2024 20:53:56 +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 1stZ1G-00EAad-PC for pgsql-in-general@arkaria.postgresql.org; Wed, 25 Sep 2024 20:53:54 +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 1stZ1G-00EAaU-Gw for pgsql-in-general@lists.postgresql.org; Wed, 25 Sep 2024 20:53:54 +0000 Received: from mail-ej1-x62f.google.com ([2a00:1450:4864:20::62f]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1stZ1C-0014xo-PI for pgsql-in-general@postgresql.org; Wed, 25 Sep 2024 20:53:53 +0000 Received: by mail-ej1-x62f.google.com with SMTP id a640c23a62f3a-a8a789c4fc5so240842366b.0 for ; Wed, 25 Sep 2024 13:53:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727297631; x=1727902431; darn=postgresql.org; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=YwWHwFoKcyJAw6BkliEtyA62l1vruYhohYAb4m0m6/M=; b=Zj91TrBq4RaegudzRdAPiAIjq7nWeVcLgiq8z9i15InIK7Phqvnp6jQInZ9eGHEeVP YjdJ4wyb0q23FlaJADwoDxw5Ve2vSxhfHzmVSnbK1PHebB6+VtzIS8jpr9UtTv7n1oi4 GYV/LToMzmrK4GhtIHB4tZGgsVJP4RFiptm2Jw+A0WR9guGzaP6W8EPc4VWZWHP3J1qM bXaxeW24RpyiGEj5tiZHriDHlnbXC1ZZFGMvxKqJ13I7O3nIe4PCxJhiwykZALSWQhYh yaYZ7fgG44O2E1y4oRD67mvdh8Nup7H3LA8iVlSgumewC0n6nlS0xFxHjh1nCv9yDBPq oLMA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727297631; x=1727902431; h=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=YwWHwFoKcyJAw6BkliEtyA62l1vruYhohYAb4m0m6/M=; b=bG6f/BmgWxOKdrjRkG/oLAP7lq/7PLljhhRFIsK/PQiIMCusoa1BkoKMSFQNJFI0pM 6CGjATy+b9qBz/YR+Y41h7j3LxfiiApsqtvJyrJtiTOBQ5/Iahn8SllqHHi2tI4mOwiM o835hg+ueFlsx8BK7+3kgB33UKZ/usReojKWTXT0d2GsoQg3rkXZv2TGM2OkOkFE/1gO /Me53M35GqxuXe/Uv4SzyezG+ghFR9W28vsi7QRMFi8jV4gi3wrCs1rsSRyIEFn3+tHt QC+H075E0f5icI7by4dCehVvhnGXp5PPE5b1lxI6nF93kHnK59oWgHKqOip2CX/X5dJC zIQQ== X-Forwarded-Encrypted: i=1; AJvYcCWNDKkWJ+oXdPplx47EzXleQDrv6VT4FS9vw5wMHFYLW1Badt68JAMeKDN+rKrMr/M3LwTBx/lpqb9mWHhCe8YK@postgresql.org X-Gm-Message-State: AOJu0YyAXi8zC65A+i9EkxRLn5KAtrwcwZVEjjC7e9AUk1paif0lGsBj I0reihC0hU78V5U/Evvy2/BNUxm39xlslffxUFSxomI5q1L2nrQvJOxFd2+TLA5UUUgtmuERdDW mIQQwSWUbHlVjLfgCe+PHXv4j0HVfVg== X-Google-Smtp-Source: AGHT+IGSgHFsJ0CmAwh4SpJEBWSrqDh/f3GH3r/5tW/Pn8gO9ldqTzJ3UCgkDMOe1vphvtCkvGoB9SCk0ReJ5ZN8k6Q= X-Received: by 2002:a17:907:36c6:b0:a8a:7884:c491 with SMTP id a640c23a62f3a-a93b15f9342mr89434266b.17.1727297631338; Wed, 25 Sep 2024 13:53:51 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Durgamahesh Manne Date: Thu, 26 Sep 2024 02:23:39 +0530 Message-ID: Subject: Re: Synchronize the dump with a logical slot with --snapshot To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org, Greg Sabino Mullane , Koichi Suzuki Content-Type: multipart/alternative; boundary="000000000000bcc77b0622f7d1cf" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000bcc77b0622f7d1cf Content-Type: text/plain; charset="UTF-8" Hi Team --snapshot=snapshotname (Use the specified synchronized snapshot when making a dump of the database This option is useful when needing to synchronize the dump with a logical replication slot) as per the pgdg How do we synchronize the dump with a logical replication slot with --snapshot? I am using the postgresql 14 version which supports only pg_create_logical_replication_slot. How to generate a internal snapshot with it ? Below CREATE_REPLICAION_SLOT not supported by postgresql 14 example osdb_lsr=# CREATE_REPLICATION_SLOT lsr_sync_01 LOGICAL pgoutput; slot_name | consistent_point | snapshot_name | output_plugin -------------+------------------+---------------------+--------------- lsr_sync_01 | 0/C000110 | 00000003-00000002-1 | pgoutput Regards, Durga Mahesh On Fri, 20 Sept, 2024, 01:27 Durgamahesh Manne, wrote: > Hi Team > > --snapshot=*snapshotname* > > (Use the specified synchronized snapshot when making a dump of the database > > This option is useful when needing to synchronize the dump with a logical > replication slot) as per the pgdg > > How do we synchronize the dump with a logical replication slot > with --snapshot? > > I am using the postgresql 14 version which supports only > pg_create_logical_replication_slot. How to generate a snapshot with it ? > > Below CREATE_REPLICAION_SLOT not supported by postgresql 14 > > example osdb_lsr=# CREATE_REPLICATION_SLOT lsr_sync_01 LOGICAL pgoutput; > slot_name | consistent_point | snapshot_name | output_plugin > -------------+------------------+---------------------+--------------- > lsr_sync_01 | 0/C000110 | 00000003-00000002-1 | pgoutput > > Regards, > > Durga Mahesh > --000000000000bcc77b0622f7d1cf Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team

--sn= apshot=3Dsnapshotname
(Use the specified synchronize= d snapshot when making a dump of the database

This option is useful when needing to synchronize the= dump with a logical replication slot) as per the pgdg

How do we synchronize the dump with a logica= l replication slot with --snapshot?

I am using the postgresql 14 version which supports only pg_cr= eate_logical_replication_slot. How to generate a internal snapshot with it = ?

Below CREATE_REPLICAIO= N_SLOT not supported by postgresql 14

example osdb_lsr=3D# CREATE_REPLICATION_SLOT lsr_sync_01 LOGI= CAL pgoutput;
=C2=A0 slot_name | consistent_point |= snapshot_name | output_plugin
-------------+-= -----------------+---------------------+---------------
=C2=A0lsr_sync_01 | 0/C000110 | 00000003-00000002-1 | pgoutput

Regards,

Durga Mahesh

=


On Fri, 20 Sept, 2024, 01:27 Durgamahesh = Manne, <maheshpostgres9@gma= il.com> wrote:
Hi Team

--snapshot=3Dsnapshotname

(Use= the specified synchronized snapshot when making a dump of the database

=

This option is useful when needin= g to synchronize the dump with a logical replication slot) as per the pgdg<= /span>

How do we synchronize the dump with a logical replicatio= n slot=C2=A0 with=C2=A0--snapshot?

I am using the postgresql 14= version which supports only pg_create_logical_replication_slot. How to gen= erate a snapshot with it ?

Below CREATE_REPLICAION_SLOT not sup= ported by postgresql 14

example osdb_lsr=3D# CREATE_REPLICATION= _SLOT lsr_sync_01 LOGICAL pgoutput;
=C2=A0 slot_name =C2=A0| consistent_= point | =C2=A0 =C2=A0snapshot_name =C2=A0 =C2=A0| output_plugin
--------= -----+------------------+---------------------+---------------
=C2=A0lsr= _sync_01 | 0/C000110 =C2=A0 =C2=A0 =C2=A0 =C2=A0| 00000003-00000002-1 | pgo= utput

Regards,

Durga Mahesh

--000000000000bcc77b0622f7d1cf--