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 1srNFK-000vs6-NT for pgsql-in-general@arkaria.postgresql.org; Thu, 19 Sep 2024 19:55:23 +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 1srNFH-0074j8-GH for pgsql-in-general@arkaria.postgresql.org; Thu, 19 Sep 2024 19:55:20 +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 1srNFH-0074iu-6Z for pgsql-in-general@lists.postgresql.org; Thu, 19 Sep 2024 19:55:20 +0000 Received: from mail-ej1-x635.google.com ([2a00:1450:4864:20::635]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1srNFF-0003ei-Ub for pgsql-in-general@postgresql.org; Thu, 19 Sep 2024 19:55:19 +0000 Received: by mail-ej1-x635.google.com with SMTP id a640c23a62f3a-a8a789c4fc5so411181166b.0 for ; Thu, 19 Sep 2024 12:55:17 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1726775716; x=1727380516; darn=postgresql.org; h=to:subject:message-id:date:from:mime-version:from:to:cc:subject :date:message-id:reply-to; bh=VuoVCqrTTVFXwPq0zhTgY8WnDv7hh56QvCshwdGgfM4=; b=mEheRzTwSxbNEIRQDWjb8d7oRSjZzGnDgjdZO7qKL9Zjc6Nf3+v9X+9JIOgvoSWVlK SqA/v931ZXDsmAEzAv7uQ+ay59dn1j0uYGvI9nfB3WCx3FIfR6R2IanJ+u3zg1C35OAw LdpLauCpbg0gv/1TNf5jXv5cQenxAuMoWoIXWOUgbiy2/YE8V9EeEZoq1BG4DXqndeN6 /54tJrqRAiAFSDbMe8vg4thgOtbrutygyLI/SMerBqiRZr/T2yETKATTRPsEg80qkrul +67/QaW5Uqvve2nDwjxJeJ0sPfxjEFa/r3u6N2N1eszuQsB4QYVYhFsaPpEE2iu4Lwn+ 7qkw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1726775716; x=1727380516; h=to:subject:message-id:date:from:mime-version:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=VuoVCqrTTVFXwPq0zhTgY8WnDv7hh56QvCshwdGgfM4=; b=LCbwMRUWIVl5bqNANA+EXGkZeLycMxmDrfr2o4GK9n/14dZQCIphqGPLWRVEXHnCWo OrLCQny6QHlMfXayr7/NTgwOoF69lisacZBZp1ZGwlyXzcbHUAvY9/TQm6ztQqG9+JLz FYx+R2FTNUt3cNZc1AGbX93STM0AUEq5471Jk8x+BQejEI9lcHI2aqbnR21yD9T/EVYh azzffB71LdqfeXnweICDUoKZfwT+EXISCSp8Ytq+MauKsV5CTK/W55dgLBqu2Ij/qcz3 tWHy/W9wMECWCuBl1x3h93mcPPpez8KRXchMbogTPsy7MGJ063tyamUEqz83yreZBLzp 7I0w== X-Forwarded-Encrypted: i=1; AJvYcCV9yPny48yR3nip9isohi1Xo50Ytdmad30Vi2jfKR0ab6kmh3ktJTZcSv7xvd2AixFqPjTtoo8+pFXaxDrYpNpe@postgresql.org X-Gm-Message-State: AOJu0YzOcDRqKS7ZpIqAnKuVyEnPsG8FD5SMdYzwDWpB5EButHdfHM80 1zieOXrOt8Y2YbGXA9Syezg9n2LN6BG/IKqCDdUrafmNNwb1CQujpfOaB3SfCIvm3snfXCs9Y/U nyxy5GQadrS1vI6cNLWUQb0gI6dM= X-Google-Smtp-Source: AGHT+IEL0IJVyW4/ISxwsmMira6CWGwm5g0Bn0xFcX1QTLROsz8xeOcog896xLClTV5O+iabuzHy7e5/cnQwxfJ3NxM= X-Received: by 2002:a17:907:980b:b0:a8d:29b7:ece3 with SMTP id a640c23a62f3a-a90d3645713mr78934266b.33.1726775716209; Thu, 19 Sep 2024 12:55:16 -0700 (PDT) MIME-Version: 1.0 From: Durgamahesh Manne Date: Fri, 20 Sep 2024 01:27:56 +0530 Message-ID: Subject: Synchronize the dump with a logical slot with --snapshot To: pgsql-general@lists.postgresql.org, pgsql-in-general@postgresql.org Content-Type: multipart/alternative; boundary="0000000000002beac606227e4dd9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000002beac606227e4dd9 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 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 --0000000000002beac606227e4dd9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Hi Team

--snapshot=3Dsnapshotname

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

This option is useful w= hen 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=C2=A0 with=C2=A0--snapshot?

I am using the pos= tgresql 14 version which supports only pg_create_logical_replication_slot. = How to generate a snapshot with it ?

Below CREATE_REPLICAION_SL= OT not supported by postgresql 14

example osdb_lsr=3D# CREATE_R= EPLICATION_SLOT lsr_sync_01 LOGICAL pgoutput;
=C2=A0 slot_name =C2=A0| c= onsistent_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-000000= 02-1 | pgoutput

Regards,

Durga Mahesh

--0000000000002beac606227e4dd9--