Re: [HACKERS] Passing query string to workers - Mailing list pgsql-hackers

From Kuntal Ghosh
Subject Re: [HACKERS] Passing query string to workers
Date
Msg-id CAGz5QCJtL497O4Ls+6BEWGVhRU4BRZw--MYpB3+=RoiLkFJu+w@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Passing query string to workers  (Rafia Sabih <rafia.sabih@enterprisedb.com>)
Responses Re: [HACKERS] Passing query string to workers  (Amit Kapila <amit.kapila16@gmail.com>)
List pgsql-hackers
On Tue, Feb 7, 2017 at 10:19 AM, Rafia Sabih
<rafia.sabih@enterprisedb.com> wrote:
> Thanks a lot Kuntal for the review, please find attached patch for the
> revised version.
Few comments on the patch:

There are some spacing issues in the code. For example,
+       estate->es_queryString = (char
*)palloc0(strlen(queryDesc->sourceText) + 1);
+       /*Estimate space for query text. */
pgindent might be helpful to track all such changes.

+#define PARALLEL_KEY_QUERY_TEXT UINT64CONST(0xE000000000000010)
I'm uncomfortable with declaring the same macro in two
files(parallel.c, execParallel.c). My suggestion would be to move
pgstat_report_activity in ParallelQueryMain instead of
ParallelWorkerMain. Then, you can remove the macro definition from
parallel.c. Thoughts?

And, the value of the macro seems pretty random to me. IMO, it should
be UINT64CONST(0xE000000000000007).

-- 
Thanks & Regards,
Kuntal Ghosh
EnterpriseDB: http://www.enterprisedb.com



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: [HACKERS] log_autovacuum_min_duration doesn't log VACUUMs
Next
From: Simon Riggs
Date:
Subject: Re: [HACKERS] Documentation improvements for partitioning