mirror of
https://github.com/postgres/postgres.git
synced 2025-10-24 01:29:19 +03:00
Revert "Enable parallel SELECT for "INSERT INTO ... SELECT ..."."
To allow inserts in parallel-mode this feature has to ensure that all the constraints, triggers, etc. are parallel-safe for the partition hierarchy which is costly and we need to find a better way to do that. Additionally, we could have used existing cached information in some cases like indexes, domains, etc. to determine the parallel-safety. List of commits reverted, in reverse chronological order:ed62d3737cDoc: Update description for parallel insert reloption.c8f78b6161Add a new GUC and a reloption to enable inserts in parallel-mode.c5be48f092Improve FK trigger parallel-safety check added by05c8482f7f.e2cda3c20aFix use of relcache TriggerDesc field introduced by commit05c8482f7f.e4e87a32ccFix valgrind issue in commit05c8482f7f.05c8482f7fEnable parallel SELECT for "INSERT INTO ... SELECT ...". Discussion: https://postgr.es/m/E1lMiB9-0001c3-SY@gemulon.postgresql.org
This commit is contained in:
@@ -466,20 +466,5 @@ extern void ParsePrepareRecord(uint8 info, xl_xact_prepare *xlrec, xl_xact_parse
|
||||
extern void EnterParallelMode(void);
|
||||
extern void ExitParallelMode(void);
|
||||
extern bool IsInParallelMode(void);
|
||||
extern void PrepareParallelModePlanExec(CmdType commandType);
|
||||
|
||||
/*
|
||||
* IsModifySupportedInParallelMode
|
||||
*
|
||||
* Indicates whether execution of the specified table-modification command
|
||||
* (INSERT/UPDATE/DELETE) in parallel-mode is supported, subject to certain
|
||||
* parallel-safety conditions.
|
||||
*/
|
||||
static inline bool
|
||||
IsModifySupportedInParallelMode(CmdType commandType)
|
||||
{
|
||||
/* Currently only INSERT is supported */
|
||||
return (commandType == CMD_INSERT);
|
||||
}
|
||||
|
||||
#endif /* XACT_H */
|
||||
|
||||
Reference in New Issue
Block a user