Re: [PERFORM] postgresql tuning with perf - Mailing list pgsql-performance

From Purav Chovatia
Subject Re: [PERFORM] postgresql tuning with perf
Date
Msg-id CADrzpjFY3tSdrGwrOMSX7B6bPNY22xnkCjRDMmVG3Fsi+SCh2w@mail.gmail.com
Whole thread Raw
In response to Re: [PERFORM] postgresql tuning with perf  (legrand legrand <legrand_legrand@hotmail.com>)
Responses Re: [PERFORM] postgresql tuning with perf
List pgsql-performance
Hi Pascal,

Do you mean the sample program that acts as the application, do you want me to share that? I can do that, but I guess my post will get blocked.

Yes, c1 is the PK. Pls see below:
bmdb=# desc dept_new
      Table "public.dept_new"
 Column |     Type      | Modifiers
--------+---------------+-----------
 c1     | numeric(10,0) | not null
 c2     | numeric(10,0) |
.
.
.
.
.
 c205   | numeric(10,0) |
Indexes:
    "dept_new_pkey" PRIMARY KEY, btree (c1)

bmdb=#

We dont analyze after loading the table. But I guess thats required only if the query plan is in doubt, lets say its doing a full table scan or alike, isnt it? That is not the case. The query is using PK index but it just seems to be slow.

Thanks

On 24 October 2017 at 01:59, legrand legrand <legrand_legrand@hotmail.com> wrote:
Hi,
could you providence the code used with PG ?
Has table dept_new an index/pk on c1 ?
Do you analyze this table after loading it ?

Regards
PAscal



--
Sent from: http://www.postgresql-archive.org/PostgreSQL-performance-f2050081.html


--
Sent via pgsql-performance mailing list (pgsql-performance@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-performance

pgsql-performance by date:

Previous
From: Purav Chovatia
Date:
Subject: Re: [PERFORM] postgresql tuning with perf
Next
From: johannes graën
Date:
Subject: Re: [PERFORM] performance drop after upgrade (9.6 > 10)