Re: add line number as prompt option to psql

From: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
To: Sawada Masahiko <sawada(dot)mshk(at)gmail(dot)com>
Cc: Jeevan Chalke <jeevan(dot)chalke(at)enterprisedb(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: add line number as prompt option to psql
Date: 2014-07-11 17:19:35
Message-ID: 20140711171935.GB6390@eldon.alvh.no-ip.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Sawada Masahiko wrote:

> As you said, if line number reached UINT_MAX then I think that this
> case is too strange.
> I think INT_MAX is enough for line number.

My point is not whether 2 billion is a better number than 4 billion as a
maximum value. My point is that wraparound of signed int is, I think,
not even defined in C, whereas wraparound of unsigned int is well
defined. cur_line should be declared as unsigned int. I don't trust
that INT_MAX+2 arithmetic.

Please don't use cur_line as a name for a global variable. Something
like PSQLLineNumber seems more appropriate if it's going to be exposed
through prompt.h. However, note that MainLoop() keeps state in local
variables and notes that it is reentrant; what happens to your cur_line
when a file is read by \i and similar? I wonder if it should be part of
PsqlScanStateData instead ...

--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2014-07-11 17:25:36 Re: tweaking NTUP_PER_BUCKET
Previous Message Sawada Masahiko 2014-07-11 17:01:35 Re: add line number as prompt option to psql