RE: Parallel INSERT (INTO ... SELECT ...)
От | tsunakawa.takay@fujitsu.com |
---|---|
Тема | RE: Parallel INSERT (INTO ... SELECT ...) |
Дата | |
Msg-id | TYAPR01MB299057A61D651E114C08F2E3FEBC0@TYAPR01MB2990.jpnprd01.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: Parallel INSERT (INTO ... SELECT ...) ("Hou, Zhijie" <houzj.fnst@cn.fujitsu.com>) |
Ответы |
RE: Parallel INSERT (INTO ... SELECT ...)
|
Список | pgsql-hackers |
From: Hou, Zhijie <houzj.fnst@cn.fujitsu.com> > IMO, max_parallel_hazard() only check the parent table's default expressions, > But if the table has partitions and its partition have its own default expressions, > max_parallel_hazard() seems does not check that. > And we seems does not check that too. > > I am not sure should we allow parallel insert for this case ? I think we can allow parallel insert in this case, because the column value is determined according to the DEFAULT definitionof the target table specified in the INSERT statement. This is described here: https://www.postgresql.org/docs/devel/sql-createtable.html "Defaults may be specified separately for each partition. But note that a partition's default value is not applied when insertinga tuple through a partitioned table." So the parallel-unsafe function should not be called. Regards Takayuki Tsunakawa
В списке pgsql-hackers по дате отправления: