pg_config --version

From: David Fetter <david(at)fetter(dot)org>
To: PostgreSQL Development <pgsql-hackers(at)postgresql(dot)org>
Subject: pg_config --version
Date: 2016-11-27 00:16:48
Message-ID: 20161127001648.GA21874@fetter.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Folks,

While updating some extensions, I noticed that pg_config --version
produces output that's...maybe not quite as useful as it might be, at
least to a machine, so I'd like to throw out some proposals to fix the
situation.

Add a --version-numeric option to pg_config

or
Replace the current --version option with its bare numeric version

or
Add another line of output to the current --version output, which
would be the numeric version by itself

I'm partial to the first because it's clear what's being asked for,
the second because the product name does nothing for comprehension,
and the third because it would be less strain on things that already
parse the output.

A somewhat larger project, not sure whether it's worth doing, would be
to enable pg_config to print arbitrary combinations of the GUCs it
could know about.

What say?

Best,
David.
--
David Fetter <david(at)fetter(dot)org> http://fetter.org/
Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter
Skype: davidfetter XMPP: david(dot)fetter(at)gmail(dot)com

Remember to vote!
Consider donating to Postgres: http://www.postgresql.org/about/donate

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dilip Kumar 2016-11-27 02:34:09 Re: Parallel bitmap heap scan
Previous Message Tom Lane 2016-11-26 22:33:56 Re: [sqlsmith] Failed assertion in TS_phrase_execute