Re: BUG #12344: libcurses issue with psql binary of Solaris package - Mailing list pgsql-bugs

From Egoitz Aurrekoetxea
Subject Re: BUG #12344: libcurses issue with psql binary of Solaris package
Date
Msg-id 272B998A-4160-45B5-B3E1-36C05E639C95@sarenet.es
Whole thread Raw
In response to BUG #12344: libcurses issue with psql binary of Solaris package  (egoitz@sarenet.es)
List pgsql-bugs
Hello!,

And by the way=E2=80=A6 have done some checks=E2=80=A6.

Have just build Postgresql 9.4.0 in Solaris 11.2 with this flags=E2=80=A6.=


export CC=3D'/usr/gcc/4.8/bin/gcc -m64'
export CXX=3D'/usr/gcc/4.8/bin/c++ -m64'
export LDFLAGS=3D'-L/usr/local/lib -R/usr/local/lib'
export CPPFLAGS=3D'-I/usr/local/include'

later=20

 ./configure --prefix=3D/tmp/postgresql-prueba
 gmake

Just for ensuring was a bug in some Solaris library=E2=80=A6=E2=80=A6 =
and not a versioning issue (the package is compiled against or =
whatever=E2=80=A6.) or whatever=E2=80=A6=20

/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql# ./psql
ld.so.1: psql: fatal: libpq.so.5: open failed: No such file or directory
Killed

It has not build libpq which I don=E2=80=99t really know why not=E2=80=A6 =
but like was just for the testing purpose=E2=80=A6. have copied the =
Postgresql binary package for Solaris libpq.so* files=E2=80=A6.

/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql# cp =
/usr/postgres/9.4-pgdg/lib/libpq.so* .

Later=E2=80=A6. have done a :=20

export =
LD_LIBRARY_PATH=3D'/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql=
'
And voil=C3=A0 :=20
/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql# ./psql
psql: FATAL:  role "root" does not exist
root@themachine:/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql# =
./psql -U thedatabase -h localhost
psql (9.4.0)
Type "help" for help.

thedatabase=3D# =
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
thedatabase-#=20
thedatabase-#=20
thedatabase-# ;
NOTICE:  identifier =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=
" will be truncated to =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
ERROR:  syntax error at or near =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa=
"
LINE 1: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa...
        ^
thedatabase=3D# select * from pg_stat_activity;
thedatabase=3D# =
aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa
thedatabase-# ;
NOTICE:  identifier =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa" =
will be truncated to =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
ERROR:  syntax error at or near =
"aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa"
LINE 1: aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa...
        ^
thedatabase=3D#=20
thedatabase=3D#=20
thedatabase=3D#=20
thedatabase=3D# \q
root@themachine:/tmp/prueba-comp-postgres/postgresql-9.4.0/src/bin/psql#=20=


It=E2=80=99s not being broken now=E2=80=A6=E2=80=A6 So perhaps is that =
it was build against for instance Solaris 11 not Solaris 11.2 and some =
issue exist with that linkage=E2=80=A6. done with a previous =
version=E2=80=A6..

If you tell me how=E2=80=A6 I wouldn=E2=80=99t mind creating it for =
Solaris 11.2 again the Postgresql package and donating it to you=E2=80=A6.=

What is the proper way of building in Solaris?? With libpq and all =
components?

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 17:07, Egoitz Aurrekoetxea <egoitz@sarenet.es> =
escribi=C3=B3:
>=20
> Good afternoon,
>=20
> 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?.
>=20
> Thank you so much,
> Best regards,
>=20
>=20
> 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.
>=20
>> El 26/12/2014, a las 16:39, Tom Lane <tgl@sss.pgh.pa.us =
<mailto:tgl@sss.pgh.pa.us>> escribi=C3=B3:
>>=20
>> egoitz@sarenet.es <mailto: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 =
<https://ftp.postgresql.org/pub/binary/v9.4.0/solaris/solaris11/i386/postg=
resql-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
>=20

pgsql-bugs by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: regression, deadlock in high frequency single-row UPDATE
Next
From: Egoitz Aurrekoetxea
Date:
Subject: Re: BUG #12344: libcurses issue with psql binary of Solaris package