On Fri, Dec 30, 2016 at 12:06 PM, ajmcello wrote:
> Reducing worker mem shaved about 12 minutes off the query time.. Thanks
> for the suggestion. I lowered it to 10MB instead of 100MB
>
> [SNIP]
>
> >>> [postgresql.conf]
> >>> max_connections = 10
> >>> max_files_per_process = 100
> >>> s
cello [mailto:ajmcell...@gmail.com]
> Sent: Freitag, 30. Dezember 2016 07:05
> To: Charles Clavadetscher
> Subject: Re: [GENERAL] performance tuning postgresql 9.5.5.10 [enterprisedb]
>
> There are no connections except one cli when running the query. After that
> finishes then I get con
Forwarding to list.
-Original Message-
From: ajmcello [mailto:ajmcell...@gmail.com]
Sent: Freitag, 30. Dezember 2016 07:05
To: Charles Clavadetscher
Subject: Re: [GENERAL] performance tuning postgresql 9.5.5.10 [enterprisedb]
There are no connections except one cli when running the
Hello
> -Original Message-
> From: pgsql-general-ow...@postgresql.org
> [mailto:pgsql-general-ow...@postgresql.org] On Behalf Of ajmcello
> Sent: Freitag, 30. Dezember 2016 05:54
> To: POSTGRES
> Subject: [GENERAL] performance tuning postgresql 9.5.5.10 [enterpri
I am trying to optimize and tune my server for fastest simple queries with
highest connection to server possible. Basically, a SELECT item from table
takes 30 minutes on a machine with SSD drives. The table has 900K entries
and 12 columns. Using that SELECT query, I then have the ability to make
a
