Re: [PATCH] pg_isready (was: [WIP] pg_ping utility) - Mailing list pgsql-hackers

From Phil Sorber
Subject Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
Date
Msg-id CADAkt-j5uE35F=Gr0eQ-K_z1iHkVwNZX_biH49fZu4nSr-2Otg@mail.gmail.com
Whole thread Raw
In response to Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)  (Fujii Masao <masao.fujii@gmail.com>)
Responses Re: [PATCH] pg_isready (was: [WIP] pg_ping utility)
List pgsql-hackers
On Fri, Feb 8, 2013 at 12:46 PM, Fujii Masao <masao.fujii@gmail.com> wrote:
> No maybe. But I think that all the client commands should follow the
> same rule. Otherwise a user would get confused when specifying
> options.

I would consider the rest of the apps using it as a consensus. I will
make sure it aligns in behavior.

>
> Regards,
>
> --
> Fujii Masao



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: function for setting/getting same timestamp during whole transaction
Next
From: Tom Lane
Date:
Subject: Re: DROP OWNED BY fails to drop privileges granted by non-owners (was Re: [GENERAL] Bug, Feature, or what else?)