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 1nnI6t-0004oV-NA for pgsql-sql@arkaria.postgresql.org; Sat, 07 May 2022 10:56:27 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nnI6q-00084S-Fo for pgsql-sql@arkaria.postgresql.org; Sat, 07 May 2022 10:56:24 +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 1nnI6q-00084J-4G for pgsql-sql@lists.postgresql.org; Sat, 07 May 2022 10:56:24 +0000 Received: from mail-ed1-x529.google.com ([2a00:1450:4864:20::529]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nnI6h-0003Av-6E for pgsql-sql@lists.postgresql.org; Sat, 07 May 2022 10:56:23 +0000 Received: by mail-ed1-x529.google.com with SMTP id g20so11256169edw.6 for ; Sat, 07 May 2022 03:56:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:from:date:message-id:subject:to; bh=TER/W08U+uT6BqQz14/SNJZhUvyrkx0FO8T5N1zj2bY=; b=dk0ibEJej8f3QM0uMjBeWL90GEsZPjmicWXea3ynsf9gsInmhTfLX/wGsjg00Ojxe/ lGqgrGsrGgh0ZDqE5ktwJ4HJtzs01zN5wK/APwbwnZem0qPOEi2luLoN+p/WZo3cbYkp 5FUUq+Se5PKrX1xajArokSPLmBo+kdzdfZ0oQPt3jyLzkSe9SqtpWiVYLE8KcnKL0thz 8CYVNXHpKIHteSNCcL66JI8K0Yo4KCxWUO962nOXyZ6FRNh5Pr8d9dnvDk/W73DT/Cgs fkTysIt9/DhE7cr4Q9vGu9mLpwhV2LfqlpC7+90rhmsYjEeQGZXRWX9ec6wCa3Isqaeh HEcA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=TER/W08U+uT6BqQz14/SNJZhUvyrkx0FO8T5N1zj2bY=; b=pWnbCgorDMUw9to4YcqlcW1pFGo0J1Xx6O7hL6wZwlxOR5xDiUy9tG1afo1PQ0nh2c IlDy/+H24xlKHbjFqO6jiGml3AkXEPMoH8Z0e2nhtd68iwV4wgdZypq40h5orh2pO4HU xcAOywT1vkJ5NCKSHfJN2DvJ4sz3dhCtOi6pjrZTfEErZ1ZKKCvuTBag5PSsNhZmlLxT 1SC/9V13shWQzLyH/GX1wX+uRjwMEoqgld1gMUAfySIVAAHo3YHSm4jy18Y6CpBpaMwb JOcZLWNkCVjfKv6kc1b/LELZobjBAP1OS71GGvRxnZ+F86A6Z5Jn8kCoN4ycdoe4u/0k /Pig== X-Gm-Message-State: AOAM533SNgHbYmAtZM4WcktWn2d9ehMa6ka6zOlLO4KOtkkfu2mjOkez WhkFwYzIceXZgCgJ/7Q4gF4KEdULcQqb3nSV6QaKKQidL3I= X-Google-Smtp-Source: ABdhPJy5BlH4oc0aXYhZVZHQBhCu/s1SN+9rgR4ux3kxiPn7V3omNxpVX717tKHKot3Cebk71AEmuqwqeZvGfZLqYCI= X-Received: by 2002:a05:6402:4414:b0:408:4dc0:3ee9 with SMTP id y20-20020a056402441400b004084dc03ee9mr8086490eda.203.1651920971886; Sat, 07 May 2022 03:56:11 -0700 (PDT) MIME-Version: 1.0 From: Shaozhong SHI Date: Sat, 7 May 2022 11:56:01 +0100 Message-ID: Subject: Ignore error and carry on To: pgsql-sql Content-Type: multipart/alternative; boundary="000000000000b9f53405de69d276" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --000000000000b9f53405de69d276 Content-Type: text/plain; charset="UTF-8" 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? Regards, David --000000000000b9f53405de69d276 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
In Python, one can do ignore error and ca= rry on processing.

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

I wish plpgsql= codes to carry on with processing others.

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

Re= gards,

David
--000000000000b9f53405de69d276--