Re: Mark btree_gist functions as PARALLEL SAFE

2020-07-20 Thread Alexander Korotkov
On Mon, Jul 20, 2020 at 3:18 PM Justin Pryzby wrote: > On Wed, Jul 15, 2020 at 03:26:24PM +0300, Alexander Korotkov wrote: > > On Thu, Jun 18, 2020 at 7:48 PM Winfield, Steven > > wrote: > > > Done - thanks again. > > > > This patch looks good to me. > > > > I'm going to push this if no objectio

Re: Mark btree_gist functions as PARALLEL SAFE

2020-07-20 Thread Justin Pryzby
On Wed, Jul 15, 2020 at 03:26:24PM +0300, Alexander Korotkov wrote: > On Thu, Jun 18, 2020 at 7:48 PM Winfield, Steven > wrote: > > Done - thanks again. > > This patch looks good to me. > > I'm going to push this if no objections. I marked as committed to make patch checker look healthier. Tha

Re: Mark btree_gist functions as PARALLEL SAFE

2020-07-15 Thread Alexander Korotkov
On Thu, Jun 18, 2020 at 7:48 PM Winfield, Steven wrote: > Done - thanks again. This patch looks good to me. I've rechecked it marks all the functions as parallel safe by installing an extension and querying the catalog. I've also rechecked that there is nothing suspicious in these functions in

Re: Mark btree_gist functions as PARALLEL SAFE

2020-06-18 Thread Winfield, Steven
Done - thanks again. Steven. From: Tom Lane Sent: 18 June 2020 16:28 To: Winfield, Steven Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Mark btree_gist functions as PARALLEL SAFE "Winfield, Steven" writes: > On the back of this thread[1]

Re: Mark btree_gist functions as PARALLEL SAFE

2020-06-18 Thread Tom Lane
"Winfield, Steven" writes: > On the back of this thread[1] over at pgsql-general, I've attached a patch > that marks the functions in btree_gist as PARALLEL SAFE. Cool, please add this patch to the commitfest queue to make sure we don't lose track of it: https://commitfest.postgresql.org/28/ (