On Mon, Nov 14, 2016 at 11:36 AM, domenico febbo
wrote:
> dear Pietro,
> are you sure about
>
> effective_io_concurrency = 30
>
> could you please explain the type of disk storage?
fast storage can certainly utilize high settings of
effective_io_concurrency at least in some cases...for example se
Dear Domenico,
I pushed a little hard on that because the virtualizer runs on a distributed
system composed by 7 clusters with more than 100 cores and an enterprise
storage. I know that usually effective_io_concurrency is set based on the
number of disks available in a RAID configuration (minus
Stephen Cresswell writes:
> I have the a table with two indexes...
(1) Tell us about the other table, mobile_summary_type.
(2) Did you transcribe the second query plan correctly? I have a hard
time believing that EXPLAIN printed two Index Cond lines for the same
indexscan.
(3) What PG version
I have the a table with two indexes...
CREATE TABLE mobile_summary_usage
(
import text,
msisdn text,
type text,
totalinteger,
day date,
cycletext
);
CREATE INDEX mobile_summary_usage_msisdn_cycle ON mobile_summary_usage
USING btree (msisdn, cycle);
CREATE I
dear Pietro,
are you sure about
effective_io_concurrency = 30
could you please explain the type of disk storage?
Il 14/Nov/2016 12:46, "Pietro Pugni" ha scritto:
> Dear list,
> I’m looking for some guidelines on how to optimize the configuration of a
> production database dedicated to a DWH ap
On Mon, Nov 14, 2016 at 4:01 AM, Seckin Pulatkan
wrote:
> Hi,
>
> On our production environment (PostgreSQL 9.4.5 on
> x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat
> 4.8.5-4), 64-bit), one of our queries runs very slow, about 5 minutes . We
> noticed that it does not us
Hi,
On our production environment (PostgreSQL 9.4.5 on
x86_64-unknown-linux-gnu, compiled by gcc (GCC) 4.8.5 20150623 (Red Hat
4.8.5-4), 64-bit), one of our queries runs very slow, about 5 minutes . We
noticed that it does not use an index that we anticapited it would.
The query is
select bookin
Dear list,
I’m looking for some guidelines on how to optimize the configuration of a
production database dedicated to a DWH application.
I run the application on different machines and have solved several issues
since now but am struggling on a production environment running Red Hat 6.7 and
Post
