Re: Recently added typedef "string" is a horrid idea - Mailing list pgsql-hackers

From Peter Geoghegan
Subject Re: Recently added typedef "string" is a horrid idea
Date
Msg-id CAM3SWZR2d=3WEpeiKCs_xo25df338kbs=s+wPLFdWb=0Gm-e6A@mail.gmail.com
Whole thread Raw
In response to Recently added typedef "string" is a horrid idea  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses Re: Recently added typedef "string" is a horrid idea
Re: Recently added typedef "string" is a horrid idea
List pgsql-hackers
On Sat, Feb 6, 2016 at 2:11 PM, Tom Lane <tgl@sss.pgh.pa.us> wrote:
> Remember that the effects of typedef names are
> *global*, so far as pgindent is concerned; not only varlena.c will
> be affected.

I'll remember that in the future.

> Please rename this typedef with some less-generic name.  Probably
> some of the other identifiers added in the same commit should be
> adjusted to match.

I suggest "VarString". All the text SortSupport routines were renamed
to match a pattern of "varstr.*" as part of the commit you mention.

The implication that was intended by the rename is that the relevant
routines are responsible for about the same cases as the cases handled
by varstr_cmp(). I tend to mostly think of the text type when looking
at varstr_cmp(), but it's also used by jsonb, for example, as well as
char(n). It has a broader purpose; it is used by collatable types
generally. So, a rename to "VarString" probably makes sense,
independent of your pgindent concern.

If this sounds like a good idea, I'll produce a patch soon.

-- 
Peter Geoghegan



pgsql-hackers by date:

Previous
From: Ashutosh Bapat
Date:
Subject: Re: postgres_fdw join pushdown (was Re: Custom/Foreign-Join-APIs)
Next
From: Craig Ringer
Date:
Subject: Re: Idle In Transaction Session Timeout, revived