Is the Halloween problem an issue in Postgres

From: guyren(at)icloud(dot)com
To: PG-General Mailing List <pgsql-general(at)postgresql(dot)org>
Subject: Is the Halloween problem an issue in Postgres
Date: 2020-12-02 20:27:16
Message-ID: 756bd845-ebe1-4c45-88e8-0ab44bbc02b7@Spark
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

The Halloween problem is that it is a challenge for the database if you’re updating a field that is also in the WHERE clause of the same query.

I just saw a presentation from someone about how in SQL Server he recommended writing changes to a temp table and then writing them to the table as being much more efficient.

Does Postgres handle this problem efficiently, or should we follow a similar strategy?

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Tom Lane 2020-12-02 20:48:05 Re: Is the Halloween problem an issue in Postgres
Previous Message Nick Cleaton 2020-12-02 16:53:38 Re: concurrent re-partitioning of declarative partitioned tables