3 ms·
We don't expose the priorities right now, but we have the priorities decay over time. That way faster queries get prioritized over long running queries. That sh
by malisper 2mo ago
We don't expose the priorities right now, but we have the priorities decay over time. That way faster queries get prioritized over long running queries. That should achieve the behavior you're looking for.
- rastignack 2mo agoYes for this particular use case it might help (no per-application aggregated temp file limit though). Also my grid workloads generate thousands of threads running queries with lots of small updates (job queues, calculation results..). I wish there was a way for postgresql to isolate those connections to a limited set of cores (or number of cores). To avoid completely saturating the server. Right now we advise using s3 and storing results in files, and asynchronously loading them with batch processes.