Re: [GENERAL] Question on session_replication_role

2015-02-13 Thread Vasudevan, Ramya
> Here's the part that's slow. The index scan on each partition is taking > ~2.5ms, and is being repeated 1847 times *for each partition*. > What is the table partitioned on? The table is partitioned on registration_id. CREATE TABLE emailsubscription.reg_email_subscriptions_p00 ( CONS

Re: [GENERAL] Question on session_replication_role

2015-02-09 Thread Jim Nasby
On 2/3/15 4:57 PM, Vasudevan, Ramya wrote: -> Append (cost=0.00..1748.87 rows=17 width=8) (actual time=11.454..11.454 rows=1 loops=1847) Buffers: shared hit=1093445 read=538 I/O Timings: read=21.060 -> Seq Scan on emailsubscription.reg

Re: [GENERAL] Question on session_replication_role

2015-02-08 Thread Vasudevan, Ramya
Jim, I am OP (Karthik)'s colleague. Please see the responses below. > Your EXPLAIN ANALYZE output doesn't show this taking 30 seconds, it shows it > taking 90ms. Please provide an EXPLAIN ANALYZE That actually demonstrates the > problem. SELECT DISTINCT it.recipient_id FROM iru.iru_tags it WHE

Re: [GENERAL] Question on session_replication_role

2015-02-02 Thread Jim Nasby
On 2/2/15 8:07 PM, Anand Kumar, Karthik wrote: 2)When we run the selects on each table separately, the query runs really fast. The moment we introduce the join (AND EXISTS), the sql takes over 30 seconds. 3)The explain plan of this query shows that Primary key on reg_email_subscriptions and uniq