f how wrong it is, until
the rows are already processed.
Furthermore: Did you think about parallel plans and most importantly cursors?
Best regards
Arne Roland
-Original Message-
From: Oliver Mattos [mailto:omat...@gmail.com]
Sent: Monday, November 13, 2017 10:52 PM
To: Arne Roland
Cc: pgsql-
ght be more
optimal to switch from a mergejoin to a hashjoin in some cases, I doubt that's
worth any work (and even less the maintenance).
Best regards
Arne Roland
-Original Message-
From: pgsql-performance-ow...@postgresql.org
[mailto:pgsql-performance-ow...@postgresql.org] On Beh
Hello,
I was encouraged to write up a few simplified, reproducible performance cases,
that occur (similarly) in our production environment. Attached you find a
generic script that sets up generic tables, used for the three different cases.
While I think at all of them
I included the times neede
