I second Art's suggestion to test whether the query is slow when run
directly against the database. If so, is some other index used, or is a
full table scan being done? If it's a full table scan even though the
index was created, you need to figure out why not (which is a question for
Postgres su
Hi all,
VACUUM ANALYSE VERBOSE ACTIVEMQ_MSGS;
=> No difference. Still slow.
I would expect the index to need to be on ID, CONTAINER for it to be used
in this query.
=> No difference, still slow. Index is not used (as shown with explain and
explain analyze)
select pid, waiting, state, query
Thank you for your answer - we have tried this before with no success.
Uli
-Ursprüngliche Nachricht-
Von: Lachezar Dobrev [mailto:l.dob...@gmail.com]
Gesendet: Montag, 24. Oktober 2016 11:42
An: users@activemq.apache.org
Betreff: Re: Persistent messages and postgres backend
You might
