|
Home > Archive > PostgreSQL Performance > August 2005 > How does the planner execute unions?
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
How does the planner execute unions?
|
|
| Chris Hoover 2005-08-26, 8:24 pm |
| Hopefully a quick question.
In 7.3.4, how does the planner execute a query with union alls in it?
Does it execute the unions serially, or does it launch a "thread" for
each union (or maybe something else entirely).
Thanks,
Chris
Here is an explain from the view I'm thinking about, how does postgres
run this query?
hmd=# explain select count(1) from clmhdr where hdr_user_id = 'user_id';
QUERY PLAN
----------------------------------------------------------------------------------------------------------------------------------------
Aggregate (cost=42.48..42.48 rows=1 width=924)
-> Subquery Scan clmhdr (cost=0.00..42.41 rows=30 width=924)
-> Append (cost=0.00..42.41 rows=30 width=924)
-> Subquery Scan "*SELECT* 1" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_live_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_live
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
-> Subquery Scan "*SELECT* 2" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_2003_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_2003
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
-> Subquery Scan "*SELECT* 3" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_2004_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_2004
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
-> Subquery Scan "*SELECT* 4" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_2005_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_2005
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
-> Subquery Scan "*SELECT* 5" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_2006_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_2006
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
-> Subquery Scan "*SELECT* 6" (cost=0.00..7.07 rows=5
width=924)
-> Index Scan using
clmhdr_2007_hdr_user
_id_hdr_clm_status_i
dx on clmhdr_2007
(cost=0.00..7.07 rows=5 width=924)
Index Cond: (hdr_user_id =
'user_id'::character
varying)
(21 rows)
hmd=#
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
| |
| Bruno Wolff III 2005-08-26, 8:24 pm |
| On Fri, Aug 26, 2005 at 16:14:18 -0400,
Chris Hoover <revoohc@gmail.com> wrote:
> Hopefully a quick question.
>
> In 7.3.4, how does the planner execute a query with union alls in it?
>
> Does it execute the unions serially, or does it launch a "thread" for
> each union (or maybe something else entirely).
Postgres doesn't have parallel execution of parts of queries. So it is
going to do one part followed by the other part.
---------------------------(end of broadcast)---------------------------
TIP 2: Don't 'kill -9' the postmaster
|
|
|
|
|