Re: proposal: alternative psql commands quit and exit - Mailing list pgsql-hackers

From Chapman Flack
Subject Re: proposal: alternative psql commands quit and exit
Date
Msg-id 5A5ADEC9.1090504@anastigmatix.net
Whole thread Raw
In response to Re: proposal: alternative psql commands quit and exit  (Everaldo Canuto <everaldo.canuto@gmail.com>)
Responses Re: proposal: alternative psql commands quit and exit
List pgsql-hackers
On 01/13/18 21:36, Everaldo Canuto wrote:

> I don't wanna be irritating but here every postgres user I found really
> can't understand how the original patch was not accepted, people against it
> did not show good reasons.

As I was watching this thread go by, the reasons being shown seemed good
to me, and they were being raised by some of the people most responsible
(as one quickly learns by scanning old archives), over the years, for
postgres being the excellent thing that it is, so it would not be my
first instinct to dismiss them.

One of the things I have come to really appreciate about this community
(in which I am still a relative newcomer) is that when disagreements arise,
you can see them being worked through by consideration of technical points
and somewhat measurable principles. In that light, if there's a better
conclusion you think is worth advocating, that would fit right in if done
in ways that respond to, and address in some way, the points already
raised; that adds more to the conversation than just saying they were
not "good".

-Chap


pgsql-hackers by date:

Previous
From: Haribabu Kommi
Date:
Subject: PQHost() undefined behavior if connecting string contains both hostand hostaddr types
Next
From: Michael Paquier
Date:
Subject: Re: PQHost() undefined behavior if connecting string contains bothhost and hostaddr types