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 1qVbJx-000gyL-7V for pgsql-general@arkaria.postgresql.org; Mon, 14 Aug 2023 17:25:37 +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 1qVbJv-006IKI-U3 for pgsql-general@arkaria.postgresql.org; Mon, 14 Aug 2023 17:25:36 +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 1qVbJv-006IKA-Gj for pgsql-general@lists.postgresql.org; Mon, 14 Aug 2023 17:25:35 +0000 Received: from mail-pl1-x634.google.com ([2607:f8b0:4864:20::634]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1qVbJs-0008Cr-PZ for pgsql-general@lists.postgresql.org; Mon, 14 Aug 2023 17:25:35 +0000 Received: by mail-pl1-x634.google.com with SMTP id d9443c01a7336-1bba48b0bd2so29941055ad.3 for ; Mon, 14 Aug 2023 10:25:32 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692033930; x=1692638730; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=Q5bJ/4IzbrmsUm0c5yCQNuFxxeCqUrInzv8DQ5uS4Io=; b=Em3/1Fkw7DE2wfsi21LimMOCoKi0Ls17HwauL1DbSdRJ5mMxHGr39JzteaFbt8lXQ/ vpukzRPaUNJCxTTw7aMb9hplzy0rp3ztvkzdNVGudBXu8VDV88ybfVWiGaMibaeMDb1e iuumicdc9btTStyBDvsmnmHBGX63qWYHdFeBN6vCxE8p6Ac80+zAss/0WBoOl4FuBrKj n4Wafxm/6biAHWayzIXAOTgx0aAaG0qQkcxCxSDBjk7kAQcz36JfSWp0DNjoI04ioJtL pm1Fy/tnDm1eMz3f3v1D5mq6x7CcPzH1dqvaFhL3W06HUUuM1R0YtdxffEMIBoRdLfI2 pBCg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692033930; x=1692638730; h=content-transfer-encoding:in-reply-to:from:references:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=Q5bJ/4IzbrmsUm0c5yCQNuFxxeCqUrInzv8DQ5uS4Io=; b=NpPSSNcrDBHnL6U519QZX2kiKBzAKqOIJQaBgrTfQDnNhoAHMEWoICoONy96Iw729q AESyiiyw2jXaGOL53AKC0BGirdUCz3liTIAH3WahQI5DY8uYIjGD/MW8cpNYXp31diad h/scGyXDyX57+2RWkVDp7dDLXsl5Z3idDY70BFGAGvusLeNWnO92NW63f0SnPltJobNY oP9pyUOlfqe6hYqSpHGVO9YZYpJkgXvYmCrq/b+053N3+Lozb0neDTCumrQfMKPu14+I /4MKW2+uSsR3SUzW3XYJAsVNjkL6KVstaw8e3JCa7BsHASnzWMICDQRq2zpKobH7Errn FKaQ== X-Gm-Message-State: AOJu0YxCYeucglk0zspltUwhiHWZ57ZdanIvlYtV9W0F7cRJbbwZAt8w vZhSHmdGzWHN+12RiyOm4WBuP/gqV3w= X-Google-Smtp-Source: AGHT+IHS7HXW57QYY4E2+97zMXU3JIf6vNt/P3ArVnWW821FYc2yyz8dhb4IuaoOT6CJDlFELoWKEg== X-Received: by 2002:a17:902:e802:b0:1bb:994c:bc43 with SMTP id u2-20020a170902e80200b001bb994cbc43mr11136392plg.18.1692033929820; Mon, 14 Aug 2023 10:25:29 -0700 (PDT) Received: from ?IPV6:2601:681:5a00:f790:3304:ead1:413c:3a13? ([2601:681:5a00:f790:3304:ead1:413c:3a13]) by smtp.gmail.com with ESMTPSA id u5-20020a170902e80500b001bc2831e1a8sm9710608plg.80.2023.08.14.10.25.28 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 14 Aug 2023 10:25:29 -0700 (PDT) Message-ID: Date: Mon, 14 Aug 2023 11:25:27 -0600 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.13.0 Subject: Re: Fatal Error : Invalid Memory alloc request size 1236252631 Content-Language: en-CA To: pgsql-general@lists.postgresql.org References: <6BDA46BE-B926-4BF7-AEBF-C9153D59A51D@a-kretschmer.de> From: Rob Sargent In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 8/14/23 09:29, Sai Teja wrote: > Could anyone please suggest any ideas to resolve this issue. > > I have increased the below parameters but still I'm getting same error. > > work_mem, shared_buffers > > Out of 70k rows in the table only for the few rows which is of large > size (700MB) getting the issue. Am unable to fetch the data for that > particular row. > > Would be appreciated if anyone share the insights. > > Thanks, > Sai > > Are you using java?  There's an upper limit on array size, hence also on String length.  You'll likely need to process the output in chunks.