Re: How bad is using queries with thousands of values for operators IN or ANY?

From: Thorsten Schöning <tschoening(at)am-soft(dot)de>
To: pgsql-general(at)postgresql(dot)org
Subject: Re: How bad is using queries with thousands of values for operators IN or ANY?
Date: 2020-08-31 09:16:22
Message-ID: 771535254.20200831111622@am-soft.de
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

Guten Tag Laurenz Albe,
am Montag, 31. August 2020 um 10:23 schrieben Sie:

> Is it an option to change that usage pattern?

Not everywhere easily, because I simply have places in which I'm
working with IDs only and e.g. need to check if they are owned by some
user. Those checks are abstracted away into individual functions
instead of JOINing always, as the latter makes queries more difficult
to maintain.

Of course there are alternatives like row level security I might have
a look at etc. And that's exactly why I asked the question, to make my
mind about that thing, if it's worth or necessary to look into
alternatives at all etc.

Mit freundlichen Grüßen,

Thorsten Schöning

--
Thorsten Schöning E-Mail: Thorsten(dot)Schoening(at)AM-SoFT(dot)de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/

Telefon...........05151- 9468- 55
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04

AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Yorwerth, Adam 2020-08-31 09:27:13 Query performance with min and filter
Previous Message Thorsten Schöning 2020-08-31 09:16:19 Re: How bad is using queries with thousands of values for operators IN or ANY?