Closed barsch closed 6 years ago
Are those entries a problem? It only occurs once on Django startup.
On 21 September 2017 at 12:02, Robert Barsch notifications@github.com wrote:
I was wondering about the countless SELECT version(); queries in my SQL log. After a bit debugging and reading https://github.com/etianen/ django-watson/blob/master/watson/backends.py I added
WATSON_BACKEND = "watson.backends.PostgresSearchBackend"
to my settings.py and those entries disappeared.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/etianen/django-watson/issues/218, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJFCMks2ThVRNWXEgbGPqaFx8uFumVfks5skkJRgaJpZM4PfJye .
they actually show up before every query which uses watson - is backend caching disabled with DEBUG=True
?
Okay, that's a bug. I've pushed a bugfix 1.4.2 release. It should be much more efficient to use the adaptive search backend.
I've also documented the setting here: https://github.com/etianen/django-watson/wiki/Database-support
On 22 September 2017 at 11:45, Robert Barsch notifications@github.com wrote:
they actually show up every query which uses watson - is backend caching disabled with DEBUG=True?
— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/etianen/django-watson/issues/218#issuecomment-331414633, or mute the thread https://github.com/notifications/unsubscribe-auth/AAJFCIkPXn5u9JbpwdeJBtUrfNNgwTWgks5sk4_bgaJpZM4PfJye .
awesome - thanks for the quick fix!
I was wondering about the countless
SELECT version();
queries in my SQL log. After a bit debugging and reading https://github.com/etianen/django-watson/blob/master/watson/backends.py I addedWATSON_BACKEND = "watson.backends.PostgresSearchBackend"
to my settings.py and those entries disappeared.