From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Phil Sorber <phil(at)omniti(dot)com> |
Cc: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: PQping command line tool |
Date: | 2012-10-04 01:18:58 |
Message-ID: | 11875.1349313538@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Phil Sorber <phil(at)omniti(dot)com> writes:
> How about adding it as an option to psql? That's not to say that I
> think we shouldn't also add it to 'pg_ctl status'.
> I was looking at the code and originally I was using return code to
> signify what the status was and some text output when quiet wasn't
> set, but psql has it's own set of established return codes. How does
> everyone feel about using different return codes when psql is in the
> PQping mode?
Personally, I think adding this to psql has nothing to recommend it:
it would be shoehorning an unrelated behavior in among what are already
too many constraints.
If we're going to do it at all, it should be a stand-alone tool.
If it's not worth that much work, it's not worth doing.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Paquier | 2012-10-04 01:19:02 | Re: Support for REINDEX CONCURRENTLY |
Previous Message | Tom Lane | 2012-10-04 01:00:27 | Re: Support for REINDEX CONCURRENTLY |