Re: Diagnosing poor insert performance in production?

From: Merlin Moncure <mmoncure(at)gmail(dot)com>
To: Wei Shan <weishan(dot)ang(at)gmail(dot)com>
Cc: Kay <kay(at)9cloud(dot)us>, pgsql novice <pgsql-novice(at)postgresql(dot)org>
Subject: Re: Diagnosing poor insert performance in production?
Date: 2015-06-11 13:48:26
Message-ID: CAHyXU0y1JCp__qmDY9fXLqNUSRAREkG9QOPuL7bOgKZkBCC1Xw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-novice

On Wed, Jun 10, 2015 at 10:26 PM, Wei Shan <weishan(dot)ang(at)gmail(dot)com> wrote:
> Hi,
>
> Could you provide more details please for us to help.
>
> 1. table definition
> 2. insert command
> 3. explain plan

Yeah, as always, please follow the guide here.
https://wiki.postgresql.org/wiki/Slow_Query_Questions

In particular, often the very first thing to determine is if you are
facing a storage (aka: i/o) based issue. Storage problems have a very
different set of resolutions.

merlin

In response to

Browse pgsql-novice by date

  From Date Subject
Next Message Jude DaShiell 2015-06-12 15:38:25 import csv file into table
Previous Message Wei Shan 2015-06-11 03:26:40 Re: Diagnosing poor insert performance in production?