Re: [PERFORM] Very slow inner join query Unacceptable latency.

2013-05-21 Thread Amit Kapila
On Wednesday, May 22, 2013 3:24 AM fburgess wrote: > The SARS_ACTS table currently has 37,115,515 rows > we have indexed: idx_sars_acts_acts_run_id ON SARS_ACTS USING btree > (sars_run_id) > we have pk constraint on the SARS_ACTS_RUN table; sars_acts_run_pkey PRIMARY > KEY (id ) > serverdb=# e

Re: [PERFORM] pg_statsinfo : error could not connect to repository

2013-05-21 Thread Amit Langote
On Tue, May 21, 2013 at 8:56 PM, Sameer Thakur wrote: > Hello, > After executing make install for pg_statsinfo when i start the server i see > error > > ERROR: could not connect to repository > WARNING: writer discards 1 items > LOG: pg_statsinfo launcher shutting down > DEBUG: shmem_exit(0): 0

Re: [PERFORM] Reliability with RAID 10 SSD and Streaming Replication

2013-05-21 Thread Greg Smith
On 5/20/13 6:32 PM, Merlin Moncure wrote: When it comes to databases, particularly in the open source postgres world, hard drives are completely obsolete. SSD are a couple of orders of magnitude faster and this (while still slow in computer terms) is fast enough to put storage into the modern a

Re: [PERFORM] Advice on tuning slow query

2013-05-21 Thread Sergey Konoplev
On Tue, May 21, 2013 at 4:16 PM, Samuel Stearns wrote: > Is there anything I can do to get the SELECT to run a little quicker. Please carefully follow the instruction first http://wiki.postgresql.org/wiki/Slow_Query_Questions. I would also suggest to upgrade postgres to the latest version, as it

[PERFORM] Advice on tuning slow query

2013-05-21 Thread Samuel Stearns
Howdy, Environment: Postgres 8.4.15 Ubuntu 10.04 Syslog view def: nms=# \d syslog View "public.syslog" Column |Type | Modifiers --+-+--- ip | inet| facility | character varying(1

Re: [PERFORM] Very slow inner join query Unacceptable latency.

2013-05-21 Thread Jaime Casanova
On Tue, May 21, 2013 at 4:53 PM, wrote: > The SARS_ACTS table currently has 37,115,515 rows > > we have indexed: idx_sars_acts_acts_run_id ON SARS_ACTS USING btree > (sars_run_id) > we have pk constraint on the SARS_ACTS_RUN table; sars_acts_run_pkey PRIMARY > KEY (id ) > > serverdb=# explain sel

[PERFORM] Very slow inner join query Unacceptable latency.

2013-05-21 Thread fburgess
The SARS_ACTS table currently has 37,115,515 rowswe have indexed: idx_sars_acts_acts_run_id ON SARS_ACTS USING btree (sars_run_id)we have pk constraint on the SARS_ACTS_RUN table; sars_acts_run_pkey PRIMARY KEY (id )serverdb=# explain select count(*) as y0_ from SARS_ACTS this_ inner join SARS_ACTS

Re: [PERFORM] performance database for backup/restore

2013-05-21 Thread Jeison Bedoya
hi jeff thanks by your answer, when you say "database objects" you talking about the tables?, because i have 1782 tables in my database. Umm, my boottleneck not is on CPU because the top don´t show something about that, the memory is used 30%, and the IO not have problem, because the Fiber ch

Re: [PERFORM] pg_statsinfo : error could not connect to repository

2013-05-21 Thread Kasahara Tatsuhito
Hello > After executing make install for pg_statsinfo when i start the server i see > error If you have any questions or troubles about pg_statsinfo, please send it to pgstatsinfo Mailing List. (http://pgfoundry.org/mail/?group_id=1000422) > postgres.conf changes made are: And you may have to cha

Re: [PERFORM] performance database for backup/restore

2013-05-21 Thread Jeff Janes
2013/5/21 Jeison Bedoya > Hi people, i have a database with 400GB running in a server with 128Gb > RAM, and 32 cores, and storage over SAN with fiberchannel, the problem is > when i go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a > restore and take a lot of 17 hours, that is

Re: [PERFORM] performance database for backup/restore

2013-05-21 Thread k...@rice.edu
On Tue, May 21, 2013 at 05:28:31PM +0400, Evgeny Shishkin wrote: > > On May 21, 2013, at 5:18 PM, Jeison Bedoya wrote: > > > Hi people, i have a database with 400GB running in a server with 128Gb RAM, > > and 32 cores, and storage over SAN with fiberchannel, the problem is when i > > go to do

Re: [PERFORM] Cost of opening and closing an empty transaction

2013-05-21 Thread Ross Reedstrom
N.B. I realize this is an ancient email, but there's a significant issue that didn't get raised. Opening a transaction and leaving it idle can be a major pain on a MVCC database like PostgreSQL. The reason is that this is the dreaded 'idle in transaction' state. If these tranactions become long l

Re: [PERFORM] performance database for backup/restore

2013-05-21 Thread Steve Crawford
On 05/21/2013 06:18 AM, Jeison Bedoya wrote: Hi people, i have a database with 400GB running in a server with 128Gb RAM, and 32 cores, and storage over SAN with fiberchannel, the problem is when i go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a restore and take a lot of 17

Re: [PERFORM] performance database for backup/restore

2013-05-21 Thread Evgeny Shishkin
On May 21, 2013, at 5:18 PM, Jeison Bedoya wrote: > Hi people, i have a database with 400GB running in a server with 128Gb RAM, > and 32 cores, and storage over SAN with fiberchannel, the problem is when i > go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a restore > and ta

[PERFORM] performance database for backup/restore

2013-05-21 Thread Jeison Bedoya
Hi people, i have a database with 400GB running in a server with 128Gb RAM, and 32 cores, and storage over SAN with fiberchannel, the problem is when i go to do a backup whit pg_dumpall take a lot of 5 hours, next i do a restore and take a lot of 17 hours, that is a normal time for that process

[PERFORM] pg_statsinfo : error could not connect to repository

2013-05-21 Thread Sameer Thakur
Hello, After executing make install for pg_statsinfo when i start the server i see error ERROR: could not connect to repository WARNING: writer discards 1 items LOG: pg_statsinfo launcher shutting down DEBUG: shmem_exit(0): 0 callbacks to make DEBUG: proc_exit(0): 0 callbacks to make DEBUG: ex