[HACKERS] Write operations in parallel mode - Mailing list pgsql-hackers

From Antonin Houska
Subject [HACKERS] Write operations in parallel mode
Date
Msg-id 18198.1503937403@localhost
Whole thread Raw
Responses Re: [HACKERS] Write operations in parallel mode  (Robert Haas <robertmhaas@gmail.com>)
List 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
visibilitychecks, and we * have no provision for broadcasting it to them. */if (IsInParallelMode())    ereport(ERROR,
        (errcode(ERRCODE_INVALID_TRANSACTION_STATE),             errmsg("cannot update tuples during aparallel
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



pgsql-hackers by date:

Previous
From: Adrien Nayrat
Date:
Subject: Re: [HACKERS] auto_explain : log queries with wrong estimation
Next
From: Aaron Patterson
Date:
Subject: [HACKERS] Custom allocators in libpq