pgsql: Fix hard-coded relkind constants in pg_dump.c.

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Fix hard-coded relkind constants in pg_dump.c.
Date: 2017-03-10 00:19:37
Message-ID: E1cm8HR-0006He-5d@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers pgsql-hackers

Fix hard-coded relkind constants in pg_dump.c.

Although it's reasonable to expect that most of these constants will
never change, that does not make it good programming style to hard-code
the value rather than using the RELKIND_FOO macros. There were only
a few such violations, and all relatively new AFAICT.

Existing style is mostly to inject relkind values into constructed
query strings using %c. I did not bother to touch places that did it
like that, but really a better technique is to stringify the RELKIND
macro, at least in places where you'd want single quotes around the
code character. That avoids any runtime effort and keeps the RELKIND
symbol close to where it's used.

Discussion: https://postgr.es/m/11145.1488931324@sss.pgh.pa.us

Branch
------
master

Details
-------
http://git.postgresql.org/pg/commitdiff/fe797b4a6a69ec0c9bf6ff992eac20c4084fda41

Modified Files
--------------
src/bin/pg_dump/pg_dump.c | 22 +++++++++++++---------
1 file changed, 13 insertions(+), 9 deletions(-)

Responses

Browse pgsql-committers by date

  From Date Subject
Next Message Andres Freund 2017-03-10 00:40:56 pgsql: Add amcheck extension to contrib.
Previous Message Robert Haas 2017-03-09 23:20:47 pgsql: Throw an error if a DATA() line contains wrong # of attributes.

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Langote 2017-03-10 00:20:51 Re: Partitioning vs ON CONFLICT
Previous Message Jeff Janes 2017-03-10 00:14:34 Re: [PATCH] Teach Catalog.pm how many attributes there should be per DATA() line