Re: Keyword table constness in jsonpath scanner.

From: Alexander Korotkov <a(dot)korotkov(at)postgrespro(dot)ru>
To: Mark G <markg735(at)gmail(dot)com>
Cc: pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Keyword table constness in jsonpath scanner.
Date: 2019-03-17 09:52:56
Message-ID: CAPpHfdtiAOUM1+EO-P9_5jRO=PFYFbNajO3FUN+XH+jrGz9Adg@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Sat, Mar 16, 2019 at 10:47 PM Mark G <markg735(at)gmail(dot)com> wrote:
> While looking over the new jsonpath stuff I noticed the keyword table
> wasn't declared const. Shouldn't the table and the actual keyword
> strings both be declared const? Perhaps something like the attached
> (untested) patch.

Looks good to me. Pushed, thanks.

------
Alexander Korotkov
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2019-03-17 10:33:32 Re: [HACKERS] PATCH: multivariate histograms and MCV lists
Previous Message Michael Paquier 2019-03-17 09:36:19 Re: Offline enabling/disabling of data checksums