16 reputation
2
bio website sorenknudsen.com
location Copenhagen
age 34
visits member for 1 year, 6 months
seen Dec 6 '12 at 10:33

Nov
14
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Added table definition
Oct
15
comment Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Ok. So first output is: pg_stat_get_live_tuples: 0 pg_stat_get_dead_tuples: 0 pg_relation_size: 29539123200 pg_total_relation_size: 32118743040 and second output is: avg: 1354.68
Oct
14
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Change actual time to reflect what I typically see. The way higher actual times where because of cache initialisation
Oct
14
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Minor change to respond to comment
Oct
10
awarded  Student
Oct
10
comment Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Added requested info. Thanks:)
Oct
10
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
added explain analyze verbose
Oct
10
comment Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
Correct. I have adjusted the code sections - the problem of course remains the same
Oct
10
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
added 7 characters in body; edited title
Oct
10
awarded  Editor
Oct
10
revised Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?
added 4 characters in body
Oct
10
asked Why does PostgreSQL aggregate result in the Index or Seq scan outputting all columns of the table?