On 10.04.2012 03:32, Jeff Janes wrote:
The To Do wiki says not to add things to the page with discussing here.
So here are some things to discuss. Assuming the discussion is a
brief yup or nope, it seems to make sense to lump them into one email:
Vacuuming a table with a large GIN index is
On Tue, Apr 10, 2012 at 7:27 AM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
I think the way we'd speed up COUNT(*) further would be to implement
materialized views. Then you could define a materialized view on COUNT(*),
and essentially get a row counter similar to MyISAM. I
On Mon, Apr 9, 2012 at 11:27 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 10.04.2012 03:32, Jeff Janes wrote:
The To Do wiki says not to add things to the page with discussing here.
...
sort_support was implemented for plain tuple sorting only, To Do is
extend to
On 10.04.2012 18:31, Jeff Janes wrote:
On Mon, Apr 9, 2012 at 11:27 PM, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 10.04.2012 03:32, Jeff Janes wrote:
The To Do wiki says not to add things to the page with discussing here.
...
sort_support was implemented for plain
On 10 April 2012 16:40, Heikki Linnakangas
heikki.linnakan...@enterprisedb.com wrote:
On 10.04.2012 18:31, Jeff Janes wrote:
If I do select count(distinct bid) from pgbench_accounts I get many
calls to btint4fastcmp, but if I do create index on pgbench_accounts
(bid) I instead get many calls
The To Do wiki says not to add things to the page with discussing here.
So here are some things to discuss. Assuming the discussion is a
brief yup or nope, it seems to make sense to lump them into one email:
Vacuuming a table with a large GIN index is painfully slow, because
the index is
