Reputation
Top tag
Next privilege 200 Rep.
See reduced ads
Badges
5
Newest
 Editor
Impact
~837 people reached

  • 0 posts edited
  • 0 helpful flags
  • 3 votes cast
Jan
12
comment In PostgreSQL, will VACUUM reset the dead tuple count (n_dead_tup in pg_stat_all_tables)?
Ok, so presumably the stats_collector should notice when the table was vacuumed?
Jan
12
revised In PostgreSQL, will VACUUM reset the dead tuple count (n_dead_tup in pg_stat_all_tables)?
added 24 characters in body
Jan
11
asked In PostgreSQL, will VACUUM reset the dead tuple count (n_dead_tup in pg_stat_all_tables)?
Jan
4
accepted PostgreSQL requires “GROUP BY” when aliasing a table?
Jan
2
answered PostgreSQL requires “GROUP BY” when aliasing a table?
Jan
2
revised PostgreSQL requires “GROUP BY” when aliasing a table?
deleted 412 characters in body
Dec
31
awarded  Editor
Dec
31
revised PostgreSQL requires “GROUP BY” when aliasing a table?
added 274 characters in body
Dec
16
comment PostgreSQL requires “GROUP BY” when aliasing a table?
You are actually right! When I replaced the UNIQUE INDEX with PRIMARY KEY, the query worked again! I'll leave this question for someone who knows what's going on to comment, I'm really interested in what is causing this.
Dec
16
comment PostgreSQL requires “GROUP BY” when aliasing a table?
It's a unique index in the child tables: for products it's: "products_pkey" PRIMARY KEY, btree (id) , and for products_active: "index_products_on_active_id" UNIQUE, btree (id)
Dec
16
asked PostgreSQL requires “GROUP BY” when aliasing a table?
Oct
5
awarded  Student
Oct
5
comment SELECT blocking SELECT?
@ypercube It won't hurt, though I don't think they are relevant. infotype: text, infowho: integer, clientidnum integer, refidnum integer, infoid integer serial primary key. Indexes on (refidnum, infotype), (clientidnum, infotype), (infowho, infotype), infoid, partial index on (refidnum, xfield, infotype) where xfield in (1,2,3). All btree. Really simple, nothing advanced.
Oct
5
comment SELECT blocking SELECT?
@a_horse_with_no_name I don't have the lock types in this report. I've added them to the query, and I have to wait for another process pile-up event to get the result.
Oct
5
comment SELECT blocking SELECT?
@a_horse_with_no_name Those queries touching the info-field are active. There is no UPDATE / INSERT anywhere to be found near those queries (I mean, I grepped it just to be sure).
Oct
5
comment SELECT blocking SELECT?
@ypercube Not without extra bureaucracy, though I can describe its features: it's very simple, there are ~~20 fields, either text, integer or date, most are null-able, no additional constraints or foreign keys, and there are ~~10 btree indexes, about half of which are composite on infotype + another field.
Oct
5
asked SELECT blocking SELECT?
Sep
29
awarded  Scholar
Sep
29
accepted PostgreSQL SQL: updating summaries
Sep
28
asked PostgreSQL SQL: updating summaries