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 1suPcm-006WXs-RC for pgsql-in-general@arkaria.postgresql.org; Sat, 28 Sep 2024 05:04:09 +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 1suPcl-002koW-VZ for pgsql-in-general@arkaria.postgresql.org; Sat, 28 Sep 2024 05:04:07 +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 1suPcl-002koO-JS for pgsql-in-general@lists.postgresql.org; Sat, 28 Sep 2024 05:04:07 +0000 Received: from mail-ej1-x62c.google.com ([2a00:1450:4864:20::62c]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1suPci-001QYx-40 for pgsql-in-general@postgresql.org; Sat, 28 Sep 2024 05:04:05 +0000 Received: by mail-ej1-x62c.google.com with SMTP id a640c23a62f3a-a8d3cde1103so354667666b.2 for ; Fri, 27 Sep 2024 22:04:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1727499842; x=1728104642; 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=B1ferAJG4x+qujiWAyWcC6kcd2vVvlR1bTlmjV6YnNs=; b=lTwStFLr4hx1WUqZT30/3kvA9zM7IgHChiIuscU5GUr+SxLPav5mQrhfexTO5zOrxw fOA0ArgJsGAXjerp/ooAKreyup60Kwm/mO9DDWMtwXdOCnIqVqnKcMYqY7rkLZp6hibm D8aNqouBI7ng7YADSSZkD7uVHTpS9n6bBefU6fhfo+n2wBriMbzEnG1sE/AbKw6roBLT CBUnz4huvBX7aKyVpnegdBE9406RVs8dQGDpt7ZVEat6krlNk4surcGk4w+UvUL3HrLh /7iDl+OOK1c6rEN0fw2KpSldgfHqjxdgifEPlSQkaJ4An3XpI5zU0jy6jUTVQOXQ3NGd 4Ocg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1727499842; x=1728104642; 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=B1ferAJG4x+qujiWAyWcC6kcd2vVvlR1bTlmjV6YnNs=; b=QO6SdTIWO3rnTPk26bvn6HYKzo/JAV9LbMxYjByZuC3aegZNMhvjDVQVTZRV2vZn3p hDtHDfizI2NXrUcxAdazb+0DG3rtruyExzmyVR4lQn5ZfKLGAInIV/v63WIl2OUj20jE aJtGc0mIkPLNcy0VbquLmGlb/7iDV5QsaY5cGXNFQ6uSuGvmr34264rXoEQzoNsBod3H 58KxP/YKouOH605BECug/T5CmK3xoZGcI/JB1DYsfDEL+jpjnS6qpszgDi1sTQ7o9rac fim4IOctMyKy6WoXW+Mlnbbkrsbt7PFDsz84pualYPK37khprFD5ODE7IoR4DwN/aid5 LweA== X-Forwarded-Encrypted: i=1; AJvYcCX2xB+QEXcomn9K4ilNZIiSPMYuBGmqtZkcCYS4p7LqlwSeg3Q6Q4KBJP9eTFPHdxkJsJ7HrfqVj3uVfl9f3/YT@postgresql.org X-Gm-Message-State: AOJu0YywcrPeVO+pTKQbJ6oXjELkMFk1PDl4AXMSdTCezBDE8zjuLqPE pi7Chv04ec467E1mNqONZAZ6ljS+YAOhzz0cKA+K+nyzZqORBaYtr0Lzvdt7qXJEMGPTlQRyvZo k96bj0UUMxyCFjU9Of30C+xY4yGIFf0+q X-Google-Smtp-Source: AGHT+IFqZ9Q8IhIJuotpCYnUqLT0FruexFINtkMj+8L8c2ai/a/6pMvJ5/V17UQetT8mEgCn9z5LifU8jULy2ViMRh8= X-Received: by 2002:a17:907:9709:b0:a8a:7b8e:fe52 with SMTP id a640c23a62f3a-a93c4a98d9dmr640501466b.59.1727499842384; Fri, 27 Sep 2024 22:04:02 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Durgamahesh Manne Date: Sat, 28 Sep 2024 10:36:52 +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="0000000000007479cd062326e647" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000007479cd062326e647 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Hi Team Can anyone respond to my question from respected team members ? Durga Mahesh On Thu, Sep 26, 2024 at 2:23=E2=80=AFAM Durgamahesh Manne wrote: > Hi Team > > --snapshot=3Dsnapshotname > (Use the specified synchronized snapshot when making a dump of the databa= se > > 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=3D# 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=3D*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 logica= l >> 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=3D# CREATE_REPLICATION_SLOT lsr_sync_01 LOGICAL pgoutpu= t; >> slot_name | consistent_point | snapshot_name | output_plugin >> -------------+------------------+---------------------+--------------- >> lsr_sync_01 | 0/C000110 | 00000003-00000002-1 | pgoutput >> >> Regards, >> >> Durga Mahesh >> > --0000000000007479cd062326e647 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team

Can anyone respond t= o my question from respected=C2=A0team members ?

D= urga Mahesh=C2=A0

On Thu, Sep 26, 2024 at 2:23=E2=80=AFAM Durgamahesh Manne = <maheshpostgres9@gmail.com<= /a>> wrote:
<= div dir=3D"auto">Hi Team

--sna= pshot=3Dsnapshotname
(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_cre= ate_logical_replication_slot. How to generate a internal snapshot with it ?=

Below CREATE_REPLICAION= _SLOT not supported by postgresql 14

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

Regards,

Durga Mahesh

<= /div>


On Fri, 20 Sept, 2024, 01:27 Durgamahesh M= anne, <ma= heshpostgres9@gmail.com> wrote:
Hi Team

--snapshot=3Dsnapshotnam= e

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

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

How do we synchr= onize the dump with a logical replication slot=C2=A0 with=C2=A0--snapshot?<= /p>

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

=

Below CREATE_REPLICAION_SLOT not supported 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 | pgoutput

Regards,

=

Durga Mahesh

--0000000000007479cd062326e647--