Home/ Questions/Q 8123663
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T06:15:00+00:00

I have a postgreSQL Server with some databases. Every user can only connect to

  • 0

I have a postgreSQL Server with some databases. Every user can only connect to certain databases.
So far so good. I wanted to test if everthing worked, so i used pgAdmin III to log in with a restricted user. when i try to connect to a database the user has no connection rights to, something seems to happen to the logfile!
it can’t be read by the server-status window anymore. All i get are a lot of messages about invalid Byte-sequences for encoding utf8.
The only way of stopping those messages windows is to kill the programm and force postgre to create a new logfile.

can anyone explain to me why that happens and how i can stop it???

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    OK, I think the problem is the “ü” in “für”. The error message seems to be complaining about a character code 0xfc which in latin1 (and similar) is lower case u with umlaut.

    Messages sent back via a database connection should be translated to the client encoding. However, the log-file contains output from a variety of sources and according to this there were issues fairly recently (2012):

    It’s a known issue, I’m afraid. The PostgreSQL postmaster logs in the
    system locale, and the PostgreSQL backends log in whatever encoding
    their database is in. They all write to the same log file, producing a
    log file full of mixed encoding data that’ll choke many text editors.

    So – I’m guessing your system locale is 8859-1 (or -15 perhaps) whereas pg-admin is expecting UTF-8. Short-term, you could set the system encoding to UTF-8, longer term drop a bug report over to the pgadmin team – one error message is helpful, after that it should probably just put hexcodes in the text or some such.

    • 0