Hi pgsql developers:
1 . Postgres 9.1, database server OS platform: Linux x86_64 and Windows
XP Professional Version 2002 SP3
Client OS platform: Linux x86_64 , Windows XP Professional Version
2002 SP3, Windows Server 2003 Standard Edition SP2
2. pgAdminIII: version 1.14.3, or the default version of Postgres 9.1
Windows x86_32
Steps:
1. Install Postgres 9.1 for Windows x86_32
2. Install the Spatial Extension for Postgis 2.0 by Stack Builder
after installing Postgres 9.1
3. Restart my computer.
4. Start pgAdminIII immediately after restart , pgAmin3 is the
default version of PG9.1, and then connect to the pg server by pgadmin3.
5. Run the SQL query: "SELECT setting FROM pg_settings WHERE name
=3D 'bytea_output'; " in pgAdmin3. It will show you the value 'escape'.
6. Run the client application 'psql' to connect to the same DB
server and database with the same user account. And in psql interactive
terminal, run the same SQL:
"SELECT setting FROM pg_settings WHERE name =3D 'bytea_output'; ". It
will show you the value 'hex', NOT the previous value 'escape'.
7. That means, the same environment, the same SQL query, but
different output. And I don't touch the file <postgresql.conf> any more
ever before.
Is this a bug of pgAdmin3?
Thanks,
Jinwei
CONFIDENTIALITY NOTICE: The information contained in this message may be pr=
ivileged and/or confidential. If you are not the intended recipient, or res=
ponsible for delivering this message to the intended recipient, any review,=
forwarding, dissemination, distribution or copying of this communication o=
r any attachment(s) is strictly prohibited. If you have received this messa=
ge in error, please notify the sender immediately, and delete it and all at=
tachments from your computer and network.
