Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnLaq-0007aH-Ps for pgsql-sql@arkaria.postgresql.org; Sat, 07 May 2022 14:39:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nnLZp-0003Yc-KN for pgsql-sql@arkaria.postgresql.org; Sat, 07 May 2022 14:38:33 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nnLZp-0003YT-8s for pgsql-sql@lists.postgresql.org; Sat, 07 May 2022 14:38:33 +0000 Received: from mail-ed1-x533.google.com ([2a00:1450:4864:20::533]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nnLZl-0004lq-HU for pgsql-sql@lists.postgresql.org; Sat, 07 May 2022 14:38:32 +0000 Received: by mail-ed1-x533.google.com with SMTP id p18so11618772edr.7 for ; Sat, 07 May 2022 07:38:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GQYFc3eUAyfnobuwi6GTst8wdTKgeppRUk8+xTjXpu0=; b=B3WQchS9UHjvDXjxCodB5NUIduuLLU8wDkMvkt3PB1R0nbzVl0Dks6BKdNwF+UqdSm yjvYf9HxU+25N7zo4M4FaQ4i0Y76ZBIGwfTJOelex2L9pjfgkyntGYHzdFMI4FnUbEDL /yzQ8tOOwD+u4mxyzP6AmXHIcoo81vlpgtW/0dsYwpv71rMA1xvv0JLTO2B+MkEOU1L6 BmL3Q+Qlmry0ekAWZrt/J8pr/OVzI6e5JEuQymmdm4bnQ4Ab5OOezJMXG317pSVK1X0A v4MnLcbHrf5XPD0kZcQFph9inmNokra2YPmhtUUXOICbW1HXyEUMJltnXJIJckOSYZcg d5sA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GQYFc3eUAyfnobuwi6GTst8wdTKgeppRUk8+xTjXpu0=; b=XFq6+MKgNN6X2BJEmdmQVUIANIjIXGqzjA1WCNzEO/NHvzLjAi7FSOIvm9rPfV/8Vv vG3z2eO4PrMtmHMIkwALAL8wmB+DszIX7rE5kz3zR//ZBxhkJrs79EhCKLPefPSCiGNc jQpe5znukkQIzJwmuTwKIbZjBsIn7247dKU5KJ5UgE6/VGkAoiMDfNzrqRKJ0NHydCuc Db96jvkgZ/dhwTggvPYWrw8YBS5YUVWY3C5BzhEJsG8rbUNCxlhJyt213WAiAQocmUdZ nvNnVt7hrwA9l+qiv4GfQBpaW4zNheXKBeL4OQT/NNAExwKWhKXm8L6Ix7cgCgqWuPMh sY8A== X-Gm-Message-State: AOAM530W58ln3Pw62I4dBoaJcfp8UuSAsMEKZFZeIoSfi04eCm/A/yCx 5WMXVIcjvfxRprIdxMiE4D9sUhVsliU5EXWHukk= X-Google-Smtp-Source: ABdhPJwbbd4iTpz0qMwAESU4RpzaQv2/X/uu0uMRerL8YW6SwV7dkWs8CogMLT5LzVRDtR3kBKqmXsgTGu0L3m3hj0Y= X-Received: by 2002:a50:c31e:0:b0:425:e127:2901 with SMTP id a30-20020a50c31e000000b00425e1272901mr8735027edb.134.1651934306783; Sat, 07 May 2022 07:38:26 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a05:640c:2bc8:b0:15b:bd92:6856 with HTTP; Sat, 7 May 2022 07:38:26 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Sat, 7 May 2022 07:38:26 -0700 Message-ID: Subject: Re: Ignore error and carry on To: Shaozhong SHI Cc: pgsql-sql Content-Type: multipart/alternative; boundary="0000000000008ca79d05de6ced63" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --0000000000008ca79d05de6ced63 Content-Type: text/plain; charset="UTF-8" On Saturday, May 7, 2022, Shaozhong SHI wrote: > In Python, one can do ignore error and carry on processing. > > I came across ERROR: invalid memory alloc request size 1073741824. > > I wish plpgsql codes to carry on with processing others. > > How to ignore error/exception and carry on in plpgsql? > Read up on the savepoint command. David J. --0000000000008ca79d05de6ced63 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable

On Saturday, May 7, 2022, Shaozhong SHI <shishaozhong@gmail.com> wrote:
In Python, one can do ign= ore error and carry on processing.

I came across ERROR:= =C2=A0 invalid memory alloc request size 1073741824.

I wish plpgsql codes to carry on with processing others.

<= /div>
How to ignore error/exception and carry on in plpgsql?

Read up on the savepoint command.

David J.
--0000000000008ca79d05de6ced63--