Re: [COMMITTERS] pgsql: pgbench: Support double constants and functions.
От | Robert Haas |
---|---|
Тема | Re: [COMMITTERS] pgsql: pgbench: Support double constants and functions. |
Дата | |
Msg-id | CA+TgmoamNxiEnLdgnBJaD1HhY9jDO=Yc6UNBRF49v2mvK8jSEw@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [COMMITTERS] pgsql: pgbench: Support double constants and functions. (Tom Lane <tgl@sss.pgh.pa.us>) |
Список | pgsql-hackers |
On Tue, Mar 29, 2016 at 12:56 AM, Tom Lane <tgl@sss.pgh.pa.us> wrote: > Michael Paquier <michael.paquier@gmail.com> writes: >> On Tue, Mar 29, 2016 at 9:52 AM, Robert Haas <rhaas@postgresql.org> wrote: >>> pgbench: Support double constants and functions. > >> Instead of INT64_MIN and INT64_MAX, I think that it would be better to >> use PG_INT64_MIN and PG_INT64_MAX. > > Indeed. > >> Note as well that DOUBLE is an >> existing variable type in VS (while INTEGER is not), > > Ooops; that one was harder to foresee. > >> A way to fix compilation here is to rename those tokens to something >> that will never conflict, like in the attached to DOUBLE_VAR and >> INTEGER_VAR, both exprparse.y and exprparse.l need an update. > > Agreed, but these symbols represent constants not variables, so > I used DOUBLE_CONST and INTEGER_CONST instead. Pushed with those > corrections, so that we can get back to looking at my own bugs :-( Oops. Thanks for cleaning up my mess. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-hackers по дате отправления: