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 1o28N8-000375-BU for pgsql-admin@arkaria.postgresql.org; Fri, 17 Jun 2022 09:34:34 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1o28N6-0000Iq-V0 for pgsql-admin@arkaria.postgresql.org; Fri, 17 Jun 2022 09:34:32 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1o28N6-0000Ig-JJ for pgsql-admin@lists.postgresql.org; Fri, 17 Jun 2022 09:34:32 +0000 Received: from mail-ej1-x636.google.com ([2a00:1450:4864:20::636]) by magus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1o28Mz-0007bV-NY for pgsql-admin@lists.postgresql.org; Fri, 17 Jun 2022 09:34:32 +0000 Received: by mail-ej1-x636.google.com with SMTP id v1so7651494ejg.13 for ; Fri, 17 Jun 2022 02:34:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=message-id:date:mime-version:user-agent:subject:content-language:to :references:from:in-reply-to:content-transfer-encoding; bh=18y6ktbRVd8QUlT5/iiMPgjpL2xER7dpWd5VMalGXv0=; b=g82k8zQhNe3MNjDdBKmJB6py0/0K6P8K5TuKk2q5xEOjJMhYnSAME1W3MTSs9z6f4X nqeNDYmL3MRVnWGbE/YXJ14o+JJS678rDIOtDTSBMs99jKXk2MlMmN2NxcrbUCzRw4n1 smLQnpK37Au2vdP9GKixxFPBKikhesyL7wPI2qQfIMcycZLmMuCh1d1sRhNX6NS27VUT giNk5cBxHghy8iWNZDfxiM6G6mjs40Q7r7zF6FXf0VKD6HievQo8pMLmPkDNS6zc8X8+ jTdQP8MRF9DpKEq4mm2EKeOlqdHT9JD/2BuwCukwMUSdpuQycmTGU8S7cF/uvvJEm+xe Rs6g== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:message-id:date:mime-version:user-agent:subject :content-language:to:references:from:in-reply-to :content-transfer-encoding; bh=18y6ktbRVd8QUlT5/iiMPgjpL2xER7dpWd5VMalGXv0=; b=jflTnbHv1yMCNqUK1j5z0jlBlgQ9WEXo82w7ZVV5cZeOIhmcIKq4kJ3DYBwkeR9Fug nqw7+ILZrfqjTbAzx6XeUpqyJKTLaAwone9n1eIYR04aVW1RTUtAdCvhMDHNaNsIbPv6 9XwsrdIlfZ23PpCKAVVP2lW8DgN8+0CtkatU8+J2YAN6UdmGI6uj6Fx1h1sZbFLZu/No m9sLfdqQf2pvwtjKnd+Db/AybkcCyp5twZ5Bblc8MNV7cZNpsmA3Yp9q+bByu/nfRV1q Q2iIOGFnDZLxkylDNCwquFAMxZ1pj/U882XbmMkkp/BWJ27myWy9HewQ1MNwcEt+4+Bo iGUQ== X-Gm-Message-State: AJIora9IoXurLI4uFWDneUJdU2sgIf3m2y4zgYMsOdaI6afVB/P4A/5l ylovLVqxNfcIXJpQBmdAN5TpQkYjVyM= X-Google-Smtp-Source: AGRyM1s5ksvmnsyJRYJ/QI3q0TnBx6bhfQuGYjk1RU+iQfnr6OiJ9hRN6iyICXBs3ng36AtDa9hDJQ== X-Received: by 2002:a17:907:9605:b0:6f5:c66:7c13 with SMTP id gb5-20020a170907960500b006f50c667c13mr8272175ejc.66.1655458464189; Fri, 17 Jun 2022 02:34:24 -0700 (PDT) Received: from [192.168.1.69] ([80.208.65.19]) by smtp.gmail.com with ESMTPSA id s11-20020a170906454b00b0071216de7710sm1902141ejq.153.2022.06.17.02.34.23 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Fri, 17 Jun 2022 02:34:23 -0700 (PDT) Message-ID: <63460d2e-7d86-95f4-483d-7168311dd901@gmail.com> Date: Fri, 17 Jun 2022 11:34:23 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0 Subject: Re: Postgres performance issue Content-Language: en-GB To: pgsql-admin@lists.postgresql.org References: From: Bo Victor Thomsen In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk https://stackoverflow.com/questions/12206600/how-to-speed-up-insertion-performance-in-postgresql And You might temporary drop the primary key when bulk loading. Med venlig hilsen / Kind regards Bo Victor Thomsen Den 16-06-2022 kl. 11:43 skrev Nikhil Ingale: > Hi All, > > I'm seeing some performance issue that's bulk inserts are around 15 > inserts per second which is very low. Do we have a performance mgmt > tool in pg like AWR in oracle? > > Regards, > Nikhil Ingale