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 1jHD7D-0001LG-VL for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Mar 2020 20:59:08 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1jHD7C-0004Bv-P9 for pgsql-bugs@arkaria.postgresql.org; Wed, 25 Mar 2020 20:59:06 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1jHD7C-00046d-DF for pgsql-bugs@lists.postgresql.org; Wed, 25 Mar 2020 20:59:06 +0000 Received: from mail-wr1-x442.google.com ([2a00:1450:4864:20::442]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1jHD79-0002zh-3T for pgsql-bugs@lists.postgresql.org; Wed, 25 Mar 2020 20:59:04 +0000 Received: by mail-wr1-x442.google.com with SMTP id t7so5084862wrw.12 for ; Wed, 25 Mar 2020 13:59:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=2ndquadrant-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=f54uEaMGU7+7tOhe9tS8aGKpthrjX4QS6TE3bA+HiyE=; b=lW/kqh8qzS6Ey0jh8BYKJtpLIOCemd28w5zrAbq03ZAPupCCPfSBa5d+12VIyQH4Hp GrrBVGjO6B4jK4i+nPogGLsAsvcck8EbKHxz7mYHlfr/GPOqz87wQZCV+uYWKXuw2921 coxAMBuauc2MenRPamenEWLe4FAJA4Vjv/13jJtPBcoEZwTbUf6u2qKiFyW3niBbnDZl ek/M343HRJLYxoqjkFJPDkKF1CLtJi3lV3Nbj9d4++o9vMj++C+R2KWWja10unXIZyBb i0KB0ho77lPkeetgbmNjeGrI2xxZknMGSmdn+uPj945BULQi/lQMz0HO4d2DxOI2h2cH v57A== 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:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=f54uEaMGU7+7tOhe9tS8aGKpthrjX4QS6TE3bA+HiyE=; b=knaKRguUFQqOmFteLt62HU3lTBjme+QvrvdmhkYuAsXNsS3uTSSkTT8Nq0W651ncGw YTYr1PaTekJx9VhYJpl507CJeHpE5bewh8JEm11rCBSyiF9OlSeprM+4I4YFOU0AoGKp RixzezLhep1zvOE+uNSKPenRkEXFrJEfBc4Lz00KWLmMlCliT693F919bzMzc/BuLMsu 1ci/sLM6Mfxoazny+/Cq/uM7JXI7eOqVM/b1N3ZUdmD1ZZUIwzN6TshoDVgV1lKazfbt fCytZGcUDtxLXxOhPry4w8odAZqoNCjfz6+YV5JEgMMRVk/Q1rEUrP9Zpq4sea8Dxagt T4YQ== X-Gm-Message-State: ANhLgQ0oTCz5nr0pz8ikLfeaywcUiKogcPpkTOBFj0TEJ5kXt42e36CY LR+9KG8IPkHnbbGZ3JKBUVeFwg== X-Google-Smtp-Source: ADFU+vuqvrkuM67QNEO3ojMJAAqCg/IMR1rmu6wRuR4hYUgfdmpH6Xi/Qknz4a4lt1m1RKGeaiKXiw== X-Received: by 2002:adf:db84:: with SMTP id u4mr5500528wri.317.1585169941210; Wed, 25 Mar 2020 13:59:01 -0700 (PDT) Received: from localhost (ip-86-49-253-141.net.upcbroadband.cz. [86.49.253.141]) by smtp.gmail.com with ESMTPSA id e9sm311223wrw.30.2020.03.25.13.59.00 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 25 Mar 2020 13:59:00 -0700 (PDT) Date: Wed, 25 Mar 2020 21:58:57 +0100 From: Tomas Vondra To: Bo Li_Chongqing University Cc: pgsql-bugs@lists.postgresql.org Subject: Re: BUG #16316: The application has lost the database connection: Message-ID: <20200325205857.c7doevpvj4y6yy2j@development> References: <16316-19aad78ae94264dd@postgresql.org> <20200325192704.ljvn4tgcjrnl76qu@development> <2089ed0f.ab6.17113435409.Coremail.boli9301@163.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Disposition: inline In-Reply-To: <2089ed0f.ab6.17113435409.Coremail.boli9301@163.com> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Thu, Mar 26, 2020 at 03:55:11AM +0800, Bo Li_Chongqing University wrote: >Hi Tomas, >Thank you very much. > > >When I want to insert into a table, if the size of table is bigger than 100 M or much more, the connection will be lost. I guess that local SQL database is not stronger to process the big data. If I limit the size to 10000, it is ok, instead, the connection will be lost. > > >I used this query in the Pgadmin to insert into a table, if I add limit 100, it works. If remove it, the connection will be lost. I just want to generate an new table in the Pgadmin >insert into variable_capacity_factor >SELECT v.generation_plant_id, t.raw_timepoint_id, round(cast(capacity_factor as numeric),7),gen_tech,load_zone_id,to_char(t.timestamp_utc,'YYYYMMDD') as timestamp >FROM a2020_new_variable_capacity_factors_historical_temp v >JOIN projection_to_future_timepoint ON(v.raw_timepoint_id = historical_timepoint_id) >JOIN a2020_new_generation_plant_scenario_member_temp USING(generation_plant_id) >JOIN sampled_timepoint_temp as t ON(t.raw_timepoint_id = future_timepoint_id) >JOIN a2020_generation_plant as t1 ON(t1.generation_plant_id = v.generation_plant_id) >WHERE generation_plant_scenario_id = 10 >AND t.time_sample_id=1 > That's neat, but it doesn't really tell us anything. Did you check the server log as I suggested? Are there any errors or interesting messages in the log? regards -- Tomas Vondra http://www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services