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 1rsUKc-007Oij-B9 for pgsql-general@arkaria.postgresql.org; Thu, 04 Apr 2024 21:09:10 +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 1rsUKb-00DP3Z-Hc for pgsql-general@arkaria.postgresql.org; Thu, 04 Apr 2024 21:09:09 +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 1rsUKb-00DP3F-5J for pgsql-general@lists.postgresql.org; Thu, 04 Apr 2024 21:09:09 +0000 Received: from mail-lf1-x12e.google.com ([2a00:1450:4864:20::12e]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rsUKY-000bvl-TC for pgsql-general@lists.postgresql.org; Thu, 04 Apr 2024 21:09:07 +0000 Received: by mail-lf1-x12e.google.com with SMTP id 2adb3069b0e04-516d15d72c3so978368e87.1 for ; Thu, 04 Apr 2024 14:09:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1712264945; x=1712869745; darn=lists.postgresql.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=y4dqGLgUpYEqD1r7ScT3PG231d4bYriiDay5UhMv+JY=; b=E5HQq9GcHhuosgJKOExXS4pbmuzTWpyrBQO4CS9wUippQEhcR58l2/v+jjABtZAdOG 2tMRTuu0IZwJ4/Y2MUhiQUJgtHqzcAkKMsXHEMHmCAcuUTvbmlxcpOVp1DoW/L0Yumy2 ns8TFld3sK+CVQLCmv7rljwecDQBgCKmlYPVC9Whr7ACFUxZCT2Tgwbq++GjB+x61H0p R/u9l+5s5OwcAqlwZqQMgXP4EyKSCStALq1BH5x7IqjAwYtoUCPHZi5L7xpLhD4pSjjh SUIp+rWOzLbtWVvrnkTRUHrMNkvP/2Gu9YidvXq769F5+E3o6xm0EBT7HviRRKXBlnUD Wlqw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1712264945; x=1712869745; h=cc: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=y4dqGLgUpYEqD1r7ScT3PG231d4bYriiDay5UhMv+JY=; b=rDFnV36xqmSOW1vH5tJHarqxB0Bnwhbrt9irT/pcyeoW2D3X+F6HaHt0SU64Bru0fS m5SnwCg6rNiDQOfIeR+VHZpVjm7mNVdEQiNMMhJNHfdQfrjLh8Tg3BtDc4oh6PBdoEc8 oT3sXGLBQJXXWmoVv/PY6PfjPJHM4+2tQPcWZvSxOddIKSe4u0QIU0iyEoNhqRzy5W8Z K4mVV6knd8rtKoa/2cOOQ00nu+K811x1+AxAM9vpGiJ1XjitpEEKuJ7XWqWUWL3n8IHw nLz/KtmXKuX4aWIqIg84T5ko7ldhZw4iquckuOrEjAGN/6emkTlfcXMYBXmhrvgmEfQw ojyA== X-Forwarded-Encrypted: i=1; AJvYcCVhpSwZZZHXo3L+qTTRkYAoucmgTpQjO3AZt3nbNIQcIFmhuOZMCt0cHXFoUmZmomu4fG4FgW9HZVc+mZbvNeb/VNiOudxQMQo1y9zQry7/wBnl X-Gm-Message-State: AOJu0YwzcoFOdPigrBYMUPayNxVuDkm8YkLikqc4YmEBzErW/1AsDg8G amQS+FJy63SkUr/SuG4BHsdoPSCvtLkZpForKSj/wHh1RcfGdWE5Y7tICUquejTHxLN0b7bXgWl pIRBoB/xXw0qpRaPTzLghocNYyVwkviswcMo= X-Google-Smtp-Source: AGHT+IF8EErqn5zJ4NvSgySKMXt9fVt0tc+RRkLGtyhpbBHnSO0BzWC+dQMfMHxVy8Rt0lLx6nKq8sQaNQuodJOlB1s= X-Received: by 2002:ac2:48a7:0:b0:513:d3cb:249f with SMTP id u7-20020ac248a7000000b00513d3cb249fmr2595170lfg.52.1712264945103; Thu, 04 Apr 2024 14:09:05 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: Greg Sabino Mullane Date: Thu, 4 Apr 2024 17:08:28 -0400 Message-ID: Subject: Re: Moving delta data faster To: yudhi s Cc: Adrian Klaver , pgsql-general Content-Type: multipart/alternative; boundary="000000000000d07de806154bbf09" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000d07de806154bbf09 Content-Type: text/plain; charset="UTF-8" So you want advice from this open source community about moving things from a proprietary database to another proprietary database, going through a proprietary storage system along the way? :) To answer the original question, use MERGE. That's it's job, and your table size is very tiny, so I doubt the performance impact will be worth worrying about. Cheers, Greg --000000000000d07de806154bbf09 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
So you want advice from this open source community about m= oving things from a proprietary=C2=A0database to another proprietary databa= se, going through a proprietary=C2=A0storage system along the way? :)
<= br>
To answer the original question, use MERGE. That's it'= ;s job, and your table size is very tiny, so I doubt the performance impact= will be worth worrying about.

Cheers,
G= reg

--000000000000d07de806154bbf09--