Good afternoon,
Thank you so much for the fast response. If I let it that way, without =
rebuilding and knowing the issue in one of the libraries mentioned=20
by you, could this just bug end by affecting the Postgresql server part =
in some way?.
Thank you so much,
Best regards,
Egoitz Aurrekoetxea
Departamento de sistemas
944 209 470
Parque Tecnol=C3=B3gico. Edificio 103
48170 Zamudio (Bizkaia)
egoitz@sarenet.es <mailto:egoitz@sarenet.es>
www.sarenet.es <http://www.sarenet.es/>
Antes de imprimir este correo electr=C3=B3nico piense si es necesario =
hacerlo.
> El 26/12/2014, a las 16:39, Tom Lane <tgl@sss.pgh.pa.us> escribi=C3=B3:
>=20
> egoitz@sarenet.es writes:
>> I'm giving a try to
>> =
https://ftp.postgresql.org/pub/binary/v9.4.0/solaris/solaris11/i386/postgr=
esql-9.4.0-S11.i386-64.tar.bz2
>> under Solaris 11.2. All seems to be running fine although I have =
found an
>> issue running the psql binary. It generates a core if you hit for =
example
>> CTRL+A after writting an amount of text. I do paste here the test =
content
>> and the core in order to fixed...
>=20
> This is evidently a bug in libreadline or libedit (whichever you're
> using), and almost certainly has nothing to do with psql proper.
>=20
> The mention of el_gets() in the stack trace makes me suspect that it's
> libedit, which is not terribly surprising because frankly we've seen a
> darn lot of nasty bugs in that library. They do fix 'em, so you could =
try
> getting a newer version of libedit. Or you could get GNU readline and
> rebuild against that. TBH I'd recommend the latter solution.
>=20
> regards, tom lane
