Write operations in parallel mode

From: Antonin Houska <ah(at)cybertec(dot)at>
To: pgsql-hackers(at)postgresql(dot)org
Subject: Write operations in parallel mode
Date: 2017-08-28 16:23:23
Message-ID: 18198.1503937403@localhost
Views: Raw Message | Whole Thread | Download mbox | Resend email
Lists: pgsql-hackers

Now that dynamic shared memory hash table has been committed
(8c0d7bafad36434cb08ac2c78e69ae72c194ca20) I wonder if it's still a big deal
to remove restrictions like this in (e.g. heap_update()):

* Forbid this during a parallel operation, lest it allocate a combocid.
* Other workers might need that combocid for visibility checks, and we
* have no provision for broadcasting it to them.
if (IsInParallelMode())
errmsg("cannot update tuples during a
parallel operation")));

Antonin Houska
Cybertec Schönig & Schönig GmbH
Gröhrmühlgasse 26
A-2700 Wiener Neustadt
Web: http://www.postgresql-support.de, http://www.cybertec.at


Browse pgsql-hackers by date

  From Date Subject
Next Message Aaron Patterson 2017-08-28 17:28:34 Custom allocators in libpq
Previous Message Adrien Nayrat 2017-08-28 15:46:48 Re: auto_explain : log queries with wrong estimation