RE: Determine parallel-safety of partition relations for Inserts

From: "Hou, Zhijie" <houzj(dot)fnst(at)cn(dot)fujitsu(dot)com>
To: Zhihong Yu <zyu(at)yugabyte(dot)com>
Cc: Greg Nancarrow <gregn4422(at)gmail(dot)com>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, vignesh C <vignesh21(at)gmail(dot)com>, "Amit Langote" <amitlangote09(at)gmail(dot)com>, David Rowley <dgrowleyml(at)gmail(dot)com>, "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Tsunakawa, Takayuki" <tsunakawa(dot)takay(at)fujitsu(dot)com>
Subject: RE: Determine parallel-safety of partition relations for Inserts
Date: 2021-02-03 01:02:45
Message-ID: 5db8ca759bcb4a1db47da01ecd04b699@G08CNEXMBPEKD05.g08.fujitsu.local
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

> For v3_0003-reloption-parallel_dml-src.patch :
> +   table_close(rel, NoLock);

> Since the rel would always be closed, it seems the return value from RelationGetParallelDML() can be assigned to a variable, followed by call to table_close(), then the return statement.

Thanks for the comment. Fixed in the latest patch.

Best regards,
houzj

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Peter Smith 2021-02-03 01:08:07 Re: Single transaction in the tablesync worker?
Previous Message Hou, Zhijie 2021-02-03 01:01:05 RE: Determine parallel-safety of partition relations for Inserts