Hello,
We have a query that is run almost each second and it's very important to
squeeze every other ms out of it. The query is:
SELECT c0."id" FROM "campaign_jobs" AS c0
WHERE (((c0."status" = $1) AND NOT (c0."id" = ANY($2
OR ((c0."status" = $3) AND (c0."failed_at" > $4))
OR ((c0."status" =
On Wednesday 28 June 2017 05:27 AM, Ulf Lohbrügge wrote:
> Hi all,
>
> we use schemata to separate our customers in a multi-tenant setup (9.5.7,
> Debian stable). Each tenant is managed in his own schema with all the tables
> that only he can access. All tables in all schemata are the same in ter
Hi all,
we use schemata to separate our customers in a multi-tenant setup (9.5.7,
Debian stable). Each tenant is managed in his own schema with all the
tables that only he can access. All tables in all schemata are the same in
terms of their DDL: Every tenant uses e.g. his own table 'address'. We
Hi Karl and Jeff,
On 26 June 2017 at 22:22, Jeff Janes wrote:
> Be warned that "explain (analyze)" can substantially slow down and distort
> this type of query, especially when sorting. You should run "explain
> (analyze, timing off)" first, and then only trust "explain (analyze)" if
> the over
