Re: libpq parameter parsing problem

--AhhlLboLdkugWU4S
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

On Tue, Jan 14, 2020 at 12:01:43PM +0530, Jobin Augustine wrote:
> Yes, agree, readability is better with that modification.
> Attaching a modified patch.

(Please always top-post, this is the style of the PostgreSQL community
mailing lists).  The new patch looks good to me, let's see if others
have extra thoughts to share.  If not, I'll try to commit it.
--
Michael

--AhhlLboLdkugWU4S
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iQIzBAABCgAdFiEEG72nH6vTowiyblFKnvQgOdbyQH0FAl4dgekACgkQnvQgOdby
QH0+Lg/+P6R23TDR97un//3gvWkAealcmTOWUnBtjVHyakPX3bO+Sj9N3CAlgtwS
A4vvdEQGw6y2+ZEQFu8t4QKVprivTLLgXAozmNPmN2RqQIRvM6uuvg2Ri2O+pT1t
67K+VwAxDL34Knk3TqTzd2mYLkZlwvJa8weZxerOj0hhsm7tVEjQOXhhxqlOZzv5
VI0bld8d1C6TX6y+uUyfmYSeRaxJ6i7Ouhsil7nLnj/HUK3RIr/WwtDpyWFPcCrF
VLuy+XFY2/dY3J95F+EMl6OuSwC19PbnTSTmMsYXwAafWuMwT7xOVm1/rf7GQsk3
E2u8KlqRPhV1UrYVm7wQ2Rs4Ikw1/gICiwFgPZX2ZOXBl5M1oEQsQn3ugpS4d6Qc
8htEUuI5L9p3okYjmt3tdwSutuvOQ1qYOpqb334MuR41zeRYAZOpA6Wc/QEpnL2M
uEePGpfSC7mPrBoFIhgoBVroVh0M+uXjLYsD6gmjiBOqxpc5n0I44MLVW1dkpvPO
GJlzSxl0HBVmVlDr+PMcQc487ybas2rboKIKqligVO6JRavISt0hksm+B4WEwhb3
BlA79XRPCuREgUAJviS+SfNgpP3QUA5gIUGFUVi1aW7FJtzYZ7iqrG6EtcqbycBM
HoRCwCaIvUMrSGlX9c54hq0b/aG+DpJ4YTmEHwEKtgsMqCAHQts=
=U1XQ
-----END PGP SIGNATURE-----

--AhhlLboLdkugWU4S--