Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from ) id 1j6bmJ-0001ba-Vo for pgsql-bugs@arkaria.postgresql.org; Tue, 25 Feb 2020 15:05:44 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1j6bmI-0008JT-D7 for pgsql-bugs@arkaria.postgresql.org; Tue, 25 Feb 2020 15:05:42 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1j6bmI-0008JM-1V for pgsql-bugs@lists.postgresql.org; Tue, 25 Feb 2020 15:05:42 +0000 Received: from mail-wm1-x342.google.com ([2a00:1450:4864:20::342]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1j6bmD-0005YW-Bo for pgsql-bugs@lists.postgresql.org; Tue, 25 Feb 2020 15:05:41 +0000 Received: by mail-wm1-x342.google.com with SMTP id a5so3361898wmb.0 for ; Tue, 25 Feb 2020 07:05:36 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=/gRmMfqy9nWrVtV/HTmrq+iqvf6oPMvMpaUEvI3otZo=; b=0+keHgzps7fOmNU4PY/pbJi044/tYXIiQSzueNMQTo07UBbd92ij2PTfOpkngyCE4b KsabyE8MLIQoqzfedRoLsNRavhayUv+NlDoIhczoppTxivCjxioLftWJ/WIV5Yu35Tk/ /QH7kc/f2a6IOyFHKoqQpmb366nzM+yMKhz3k1ANIRlMHeJ+1eWFvOE56AlkM0RZPssO kwv5M1soW9E9bqQibPKTqikOK0urHSv2hhbwnJcGtNju6MveIPPqVe0Ia2GAFQK8s4sJ 4FwlrSERnuld+iIdD0J7ZU/J73jTo2PkpIG0iGU7l679gaJ/ukht4E9jpTL1QmX99/8i EQ3g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=/gRmMfqy9nWrVtV/HTmrq+iqvf6oPMvMpaUEvI3otZo=; b=tkYyBBh8NP1MFVQWoMjmqDdgZJHj7+QN+/bCUR9VCndehT+6GUHWIiPvKTlOxgFzbk j/Qh3B3qRZB47PG8wrqbTy8oWZ0K1cbNWbNkN6vUnts4uyqLFZ5getZUlpPdiKUbtk3E adl9vT1sw1Rps/d+HBn9yctuGnSkvq4BSqX7rYxJDpC4ty6Rgi7TuGJHAZqhlbGSUW+m /r7EH/1kD7kXLTnuFNMXjkcArDoeY6Vnx3VpO0mqX3YJ+pSbPjW1Hf70YMGlzoU7rgw7 +KGyDrh+azumQdUU6PY99GxSN7bPsfTLqc7RSj1S16p07gB1w4xLbaBJ1MY98jWMDaOP Cgfg== X-Gm-Message-State: APjAAAVFAQ5cWe5poGNbaF3cDQaH3mHQvJGF8JzTS0UNI43v5jLySlUQ KDa3t+QmFtwg1228uPbdk6QRrQ== X-Google-Smtp-Source: APXvYqz0/4tZKvgCukGw8zwXismrU0lw4zNMk3+RmwjLn/trNO+w9Mmp206YZyhjU7WaqtNuJDux4A== X-Received: by 2002:a05:600c:149:: with SMTP id w9mr5428726wmm.132.1582643136405; Tue, 25 Feb 2020 07:05:36 -0800 (PST) Received: from localhost (static-84-42-175-93.net.upcbroadband.cz. [84.42.175.93]) by smtp.gmail.com with ESMTPSA id s23sm24841685wra.15.2020.02.25.07.05.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 25 Feb 2020 07:05:35 -0800 (PST) Date: Tue, 25 Feb 2020 16:05:34 +0100 From: Tomas Vondra To: prachi.prachi97ps@gmail.com, pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16275: we are facing error as psycopg2.errors.ProgramLimitExceeded: row is too big: size 24520, maximum Message-ID: <20200225150534.bsjf3uwemiwwpbzg@development> References: <16275-8fa8cffdeec4d69b@postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <16275-8fa8cffdeec4d69b@postgresql.org> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Tue, Feb 25, 2020 at 06:49:06AM +0000, PG Bug reporting form wrote: >The following bug has been logged on the website: > >Bug reference: 16275 >Logged by: prachi surangalikar >Email address: prachi.prachi97ps@gmail.com >PostgreSQL version: 12.0 >Operating system: windows 10 >Description: > >i am trying this program using python, i followed the steps but it did not >helped; how can i solve this error please tell us > This simply meas that you're trying to insert data into a table, but the resulting row is far too wide (it needs to fit into 8kB data page, but it's way larger than that). What exactly is happening depends on how is the table defined. Maybe it has too many columns, or maybe the columns are wide enough to overflow the page. Or something like that. In general, I doubt this is a bug - it's expected behavior, essentially an implementation limitation. But it's hard to say unless you show us the table schema. regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services