Re: Make better use of existing enums in plpgsql - Mailing list pgsql-hackers

From Pavel Stehule
Subject Re: Make better use of existing enums in plpgsql
Date
Msg-id CAFj8pRC6SSCEtbr0+2jrq8KqWwLzF9TNwrTiq+r3aUvcVNZ05Q@mail.gmail.com
Whole thread Raw
In response to Make better use of existing enums in plpgsql  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: Make better use of existing enums in plpgsql  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
List pgsql-hackers
Hi

2016-08-19 16:56 GMT+02:00 Peter Eisentraut <peter.eisentraut@2ndquadrant.com>:
plpgsql.h defines a number of enums, but most of the code passes them
around as ints.  The attached patch updates structs and function
prototypes to take enum types instead.  This clarifies the struct
definitions in plpgsql.h in particular.

I am sending review of this trivial patch.

1. No problems with patching, compiling
2. all regress tests passed
3. There are not any visible change, so tests, docs are not necessary
4. Using enum instead int is generally good idea

I will mark this patch as ready for commiters.
 

I didn't deal with the PLPGSQL_RC_* symbols, since they are only used in
pl_exec.c (could be moved there?), and it would bloat this patch.

It is good idea. PLPGSQL_RC_* should be private in pl_exec.c

Regards

Pavel
 

--
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Remove superuser() checks from pgstattuple
Next
From: Tom Lane
Date:
Subject: Re: Transactional enum additions - was Re: Alter or rename enum value