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 1rw4Ln-00GY3V-UJ for pgsql-general@arkaria.postgresql.org; Sun, 14 Apr 2024 18:13:11 +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 1rw4Kn-007ers-JH for pgsql-general@arkaria.postgresql.org; Sun, 14 Apr 2024 18:12:09 +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 1rw4Kn-007erj-6B for pgsql-general@lists.postgresql.org; Sun, 14 Apr 2024 18:12:09 +0000 Received: from mail-oa1-x2d.google.com ([2001:4860:4864:20::2d]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1rw4Kh-000w1I-Cd for pgsql-general@lists.postgresql.org; Sun, 14 Apr 2024 18:12:08 +0000 Received: by mail-oa1-x2d.google.com with SMTP id 586e51a60fabf-22ed075a629so1619342fac.3 for ; Sun, 14 Apr 2024 11:12:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1713118321; x=1713723121; 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=3diiZC5lpv1KTLRdY1ibeguEWmJvnMMbj+4Ok4P7QiU=; b=US7+kxFEJGuk0X81efaa9ix+Hc7Uy0ZVS3TIe3frPSdtV8wqxzcGHm4FsKi7bRxglc 9gr+OcoLKm4sa3VAM0rKrzxFkhEHWNvQR9didfomvuDxI1qV5wGdEgdI4lJV2X1mDoTH fx+90DHlRZQg+4QrDRDdcLYgxDho1wxfy4qaBlov1lJOoAABd0YHe2ivJ1cvXm3sR+sl Oh3eTuhQhKusCxik/rpMboY85SMNO6huJ0xU3WoGpTHuQeTuaM719oF5Tu5pyH7VqRML ASBtOJeWCHE5INp2RF+Y5DE9Pl3VXfqD/ifKG/jrR5u+v3XJKHQxbkWfpHoqAlHbVTBi FMlQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1713118321; x=1713723121; 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=3diiZC5lpv1KTLRdY1ibeguEWmJvnMMbj+4Ok4P7QiU=; b=V+pIM+9ukHJM8XtqP48/J6EQk7Ax9qDIqr+eOGQloPR4I3Rxek0RuKqry/Nqfvfnh0 h82xLy3ZLVgtAv1/q0oT1k5QquhO0jNL+MIJ3DI9V/m3r5E2jOAGGWryILVbg1DdGYA6 8zvmfpdjBB+1CzHd6WVxm4UwXRZGYZte8a3LmT5EG6NMr/36/TLZBgLDmuNJwB4a4ouV JpFINFY4SeD8rGYzu/mQMgWmi/NZzFdBJtTXnuozyZyYESedAR5Iv2gWtEQ81C4AxKHg JAzWLCtvYS3O31VFd0RRl/dx7A+uhU2vTxTC6al7Qhb4RxcWi1fmQ62MppeqqHz0i5jN N2CQ== X-Forwarded-Encrypted: i=1; AJvYcCU93yHyCvjTyApGDZKZ1WeGUBEj2frSmw1dLX4xbq+t9m6tWval4EFP6N7ZuyWMyO2EWsk9lExcZUEoJpuTjXoy7llyKGKOEJn7y0KSHa/o8Dw2 X-Gm-Message-State: AOJu0YxbRW47Tk6CgJIwb592CozKMr4lSw4LSWe7C3qRy7/Rzqpfp9gk Peug0ux0zU5W+jbIGLyQa9c+Gbtx7+3RdXHnzwRwp0rKJ9ebm+KimazxBz5f4DhpPD9gmOhrukq Yx2CTsiPLU6wQ8N9txXKW/bFusSk= X-Google-Smtp-Source: AGHT+IHI3kA7JzpJG7bpE1pWNIFLIok7gcw9230/7mifDbRF3qj5WE4aJVjy5xcDXaxmBmvlE4k1V8HCB82rbF8Mn5I= X-Received: by 2002:a05:6870:c351:b0:233:3085:e55c with SMTP id e17-20020a056870c35100b002333085e55cmr9320182oak.53.1713118321095; Sun, 14 Apr 2024 11:12:01 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: "David G. Johnston" Date: Sun, 14 Apr 2024 11:11:23 -0700 Message-ID: Subject: Re: constant crashing To: Francisco Olarte Cc: jack , "pgsql-general@lists.postgresql.org" Content-Type: multipart/alternative; boundary="000000000000fcbd080616127025" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000fcbd080616127025 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Sun, Apr 14, 2024 at 10:20=E2=80=AFAM Francisco Olarte wrote: > > If postgres does not supress redundant updates ( lots of people can > answer that ) It does not. My other usual piece of advice along these lines, if doing the transform outside the database is not desirable, is to at least ensure you are doing them on a staging table that is defined as either being temporary or unlogged. WAL production probably isn't causing the crash but can definitely be an issue and is pointless to incur during most transformation processing. David J. --000000000000fcbd080616127025 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
On Sun, Apr 14, 2024 at 10:20=E2=80=AFAM Francisco Olarte = <folarte@peoplecall.com>= ; wrote:

If postgres does not supress redundant updates ( lots of people can
answer that )

It does not.=C2=A0 My other usu= al piece of advice along these lines, if doing the transform outside the da= tabase is not desirable, is to at least ensure you are doing them on a stag= ing table that is defined as either being temporary or unlogged.=C2=A0 WAL = production probably isn't causing the=C2=A0crash but can definitely be = an issue and is pointless to incur during most transformation processing.

David J.

--000000000000fcbd080616127025--