Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
Facebook
Downloads
Home
>
mailing lists
how does the planer to estimate row when i use order by and group by - Mailing list pgsql-performance
From
楊新波
Subject
how does the planer to estimate row when i use order by and group by
Date
August 12, 2014
05:59:15
Msg-id
CAK=TrEEHgo9Lwk3O5MQqqjUTX=21-zTyNaeqKdhhXyhBsKqhLA@mail.gmail.com
Whole thread
Raw
Responses
Re: how does the planer to estimate row when i use order by and group by
(Marti Raudsepp <marti@juffo.org>)
List
pgsql-performance
Tree view
hi ,everybody
why does the planer estimate 200 rows when i use order by and group by .
evn:postgresql 8.4 and 9.3
table:
CREATE TABLE a
(
id serial NOT NULL,
name character varying(20),
modifytime timestamp without time zone,
CONSTRAINT a_pk PRIMARY KEY (id)
)
SQL:
explain analyze
select * from
( select id from a order by id ) d
group by id;
Query plan:
"Group (cost=0.15..66.42 rows=200 width=4) (actual time=0.008..0.008 rows=0 loops=1)"
" -> Index Only Scan using a_pk on a (cost=0.15..56.30 rows=810 width=4) (actual time=0.006..0.006 rows=0 loops=1)"
" Heap Fetches: 0"
"Total runtime: 0.046 ms"
Can anybody suggest something or explain this behavior?
pgsql-performance
by date:
Previous
From:
Maxim Boguk
Date:
09 August 2014, 07:22:48
Subject:
Re: Optimization idea for long IN() lists
Next
From:
Mark Kirkwood
Date:
12 August 2014, 07:56:27
Subject:
Re: 60 core performance with 9.3
Есть вопросы? Напишите нам!
Соглашаюсь с условиями обработки персональных данных
I confirm that I have read and accepted PostgresPro’s
Privacy Policy
.
I agree to get Postgres Pro discount offers and other marketing communications.
✖
×
×
Everywhere
Documentation
Mailing list
List:
all lists
pgsql-general
pgsql-hackers
buildfarm-members
pgadmin-hackers
pgadmin-support
pgsql-admin
pgsql-advocacy
pgsql-announce
pgsql-benchmarks
pgsql-bugs
pgsql-chat
pgsql-cluster-hackers
pgsql-committers
pgsql-cygwin
pgsql-docs
pgsql-hackers-pitr
pgsql-hackers-win32
pgsql-interfaces
pgsql-jdbc
pgsql-jobs
pgsql-novice
pgsql-odbc
pgsql-patches
pgsql-performance
pgsql-php
pgsql-pkg-debian
pgsql-pkg-yum
pgsql-ports
pgsql-rrreviewers
pgsql-ru-general
pgsql-sql
pgsql-students
pgsql-testers
pgsql-translators
pgsql-www
psycopg
Period
anytime
within last day
within last week
within last month
within last 6 months
within last year
Sort by
date
reverse date
rank
Services
24×7×365 Technical Support
Migration to PostgreSQL
High Availability Deployment
Database Audit
Remote DBA for PostgreSQL
Products
Postgres Pro Enterprise
Postgres Pro Standard
Cloud Solutions
Postgres Extensions
Resources
Blog
Documentation
Webinars
Videos
Presentations
Community
Events
Training Courses
Books
Demo Database
Mailing List Archives
About
Leadership team
Partners
Customers
In the News
Press Releases
Press Info
By continuing to browse this website, you agree to the use of cookies. Go to
Privacy Policy
.
I accept cookies