[BUGS] BUG #2692: psql sends natively-localized strings to database without setting client_encoding first
The following bug has been logged online: Bug reference: 2692 Logged by: Sergiy Vyshnevetskiy Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.4 Operating system: FreeBSD-6 stable Description:psql sends natively-localized strings to database without setting client_encoding first Details: psql mixes natively-localized string in SQL commands without setting client_encoding first. Looks like we _really_ need some code in configure script to find acceptable native names for our database charsets. %zsh 1 11:27 [EMAIL PROTECTED] p0 /home/serg set | egrep -a '^LANG|^LC_|^MM_CHAR' LANG=ru_RU.KOI8-R MM_CHARSET=KOI8-R %zsh 0 11:27 [EMAIL PROTECTED] p0 /home/serg psql -l ERROR: invalid byte sequence for encoding "UTF8": 0xe9cdd1 %zsh 1 11:27 [EMAIL PROTECTED] p0 /home/serg psql -d postgres SET Welcome to psql 8.1.4, the PostgreSQL interactive terminal. Type: \copyright for distribution terms \h for help with SQL commands \? for help with psql commands \g or terminate with semicolon to execute query \q to quit #psql = [EMAIL PROTECTED]:5432 postgres \encoding KOI8 #psql = [EMAIL PROTECTED]:5432 postgres \l СпиÑок баз даннÑÑ ÐÐ¼Ñ | ÐÐ»Ð°Ð´ÐµÐ»ÐµÑ | ÐодиÑовка +--+--- postgres | pgsql| UTF8 template0 | pgsql| UTF8 template1 | pgsql| UTF8 (запиÑей: 3) #psql = [EMAIL PROTECTED]:5432 postgres ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #2692: psql sends natively-localized strings to database without setting client_encoding first
"Sergiy Vyshnevetskiy" <[EMAIL PROTECTED]> writes: > psql mixes natively-localized string in SQL commands without setting > client_encoding first. Looks like we _really_ need some code in configure > script to find acceptable native names for our database charsets. Actually, psql has no business sending those strings to the server at all --- it's just laziness in describe.c not to find another method of attaching the headings to the output tables ... regards, tom lane ---(end of broadcast)--- TIP 6: explain analyze is your friend
[BUGS] BUG #2688: Building from source with PL/Python fails ("distutils not found")
My yesterday bug-report #2688 is solved. The solution was that I would
have need to set the path environment to the shared libraries after I
built Python with the --enable-shared option. A Linux newbie error. I
will ask the Python doc team to add a notice on the appropriate place.
Sorry for the inconvience.
Anastasios
Subject:
BUG #2688: Building from source with PL/Python fails ("distutils not found")
From:
"Anastasios Hatzis" <[EMAIL PROTECTED]>
Date:
Wed, 11 Oct 2006 18:45:35 GMT
To:
pgsql-bugs@postgresql.org
The following bug has been logged online:
Bug reference: 2688
Logged by: Anastasios Hatzis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2beta1
Operating system: openSUSE Linux 10.0 - 64bit
Description:Building from source with PL/Python fails ("distutils
not found")
Details:
OS: A clean, fresh, minimalistic installation of openSUSE Linux 10.0 - 64bit
on AMD Opteron 146 CPU. I added GCC-C++ package and dependent packages.
Details on request if needed.
A1) Building successfully Python 2.5 (final) from source:
# ./configure --enable-shared
# make
# make test
# make install
A2) Since at step B) problem occurred as described in C) I repeated Python
installation with explicit distutils option and tried again B) - but also
with same result as in C):
# make clean
# ./configure --enable-shared --with-distutils
# make
# make test
# make install
B) Building PostgreSQL 8.2-beta1 from source:
# ./configure --with-python --with-openssl --enable-thread-safety
C) Leads to this error:
...
checking for python... /usr/local/bin/python
checking for Python distutils module... no
configure: error: distutils module not found
#
D)
But there is distutils in my Python installation:
/usr/local/lib/python2.5/distutils/
In the printed directory usr/local/bin/python the following files of
interest reside:
-rwxr-xr-x 2 root root 11912 Oct 11 20:25 python
lrwxrwxrwx 1 root root16 Oct 11 20:25 python-config ->
python2.5-config
-rwxr-xr-x 2 root root 11912 Oct 11 20:25 python2.5
-rwxr-xr-x 1 root root 1281 Oct 11 20:25 python2.5-config
Probably I made a mistake during compilation? Or is this a problem of
8.2-beta1 with PL/Python on 64bit?
Many thanks!
--- Begin Message ---
The following bug has been logged online:
Bug reference: 2688
Logged by: Anastasios Hatzis
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.2beta1
Operating system: openSUSE Linux 10.0 - 64bit
Description:Building from source with PL/Python fails ("distutils
not found")
Details:
OS: A clean, fresh, minimalistic installation of openSUSE Linux 10.0 - 64bit
on AMD Opteron 146 CPU. I added GCC-C++ package and dependent packages.
Details on request if needed.
A1) Building successfully Python 2.5 (final) from source:
# ./configure --enable-shared
# make
# make test
# make install
A2) Since at step B) problem occurred as described in C) I repeated Python
installation with explicit distutils option and tried again B) - but also
with same result as in C):
# make clean
# ./configure --enable-shared --with-distutils
# make
# make test
# make install
B) Building PostgreSQL 8.2-beta1 from source:
# ./configure --with-python --with-openssl --enable-thread-safety
C) Leads to this error:
...
checking for python... /usr/local/bin/python
checking for Python distutils module... no
configure: error: distutils module not found
#
D)
But there is distutils in my Python installation:
/usr/local/lib/python2.5/distutils/
In the printed directory usr/local/bin/python the following files of
interest reside:
-rwxr-xr-x 2 root root 11912 Oct 11 20:25 python
lrwxrwxrwx 1 root root16 Oct 11 20:25 python-config ->
python2.5-config
-rwxr-xr-x 2 root root 11912 Oct 11 20:25 python2.5
-rwxr-xr-x 1 root root 1281 Oct 11 20:25 python2.5-config
Probably I made a mistake during compilation? Or is this a problem of
8.2-beta1 with PL/Python on 64bit?
Many thanks!
--- End Message ---
---(end of broadcast)---
TIP 1: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to [EMAIL PROTECTED] so that your
message can get through to the mailing list cleanly
[BUGS] BUG #2691: Server did not start. Error: Could not create log file.
The following bug has been logged online: Bug reference: 2691 Logged by: Ille vieljans Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1 Operating system: debian Description:Server did not start. Error: Could not create log file. Details: Stopping PostgreSQL 8.1 database server: main. hostname:/etc/init.d# ./postgresql-8.1 start Starting PostgreSQL 8.1 database server: main* Use of uninitialized value in pattern match (m//) at /usr/share/postgresql-common/PgCommon.pm line 433. Error: Could not create log file failed! --- Remark: I did not change anything at postgres. I configured postfix, shutdown server. On restart postgres did not start, error message above. I repeated, the same error. ---(end of broadcast)--- TIP 2: Don't 'kill -9' the postmaster
[BUGS] BUG #2690: GRANT does not allow periods in database or schema names
The following bug has been logged online: Bug reference: 2690 Logged by: Nick Johnson Email address: [EMAIL PROTECTED] PostgreSQL version: 8.1.1 Operating system: FreeBSD 6.1 Description:GRANT does not allow periods in database or schema names Details: Though you can create a database with a period in the name (e.g., "example.com"), you cannot issue a GRANT on that database name from the command line. pgsql=# GRANT ALL ON DATABASE example.com TO someuser; ERROR: syntax error at or near "." at character 30 LINE 1: GRANT ALL ON DATABASE example.com TO someuser; The same syntax works okay for databases without a period in the name. Either GRANT should work on any database name that works when creating a database, or CREATE should disallow the same things that GRANT disallows. ---(end of broadcast)--- TIP 3: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faq
Re: [BUGS] BUG #2690: GRANT does not allow periods in database or schema names
Nick Johnson wrote: > > The following bug has been logged online: > > Bug reference: 2690 > Logged by: Nick Johnson > Email address: [EMAIL PROTECTED] > PostgreSQL version: 8.1.1 > Operating system: FreeBSD 6.1 > Description:GRANT does not allow periods in database or schema names > Details: > > Though you can create a database with a period in the name (e.g., > "example.com"), you cannot issue a GRANT on that database name from the > command line. Sure you can. Just quote the name: GRANT ALL ON DATABASE "example.com" TO someuser; -- Alvaro Herrerahttp://www.CommandPrompt.com/ The PostgreSQL Company - Command Prompt, Inc. ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #2690: GRANT does not allow periods in database or schema names
Nick Johnson wrote: > Though you can create a database with a period in the name (e.g., > "example.com"), you cannot issue a GRANT on that database name from > the command line. > > pgsql=# GRANT ALL ON DATABASE example.com TO someuser; > ERROR: syntax error at or near "." at character 30 You are making the faulty assumption that example.com and "example.com" are the same thing. -- Peter Eisentraut http://developer.postgresql.org/~petere/ ---(end of broadcast)--- TIP 6: explain analyze is your friend
Re: [BUGS] BUG #2690: GRANT does not allow periods in database or schema names
"Nick Johnson" <[EMAIL PROTECTED]> writes: > Though you can create a database with a period in the name (e.g., > "example.com"), you cannot issue a GRANT on that database name from the > command line. You need some double quotes: http://www.postgresql.org/docs/8.1/static/sql-syntax.html#SQL-SYNTAX-IDENTIFIERS This is by no means unique to GRANT, nor to database names. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] BUG #2691: Server did not start. Error: Could not create log file.
"Ille vieljans" <[EMAIL PROTECTED]> writes: > Stopping PostgreSQL 8.1 database server: main. > hostname:/etc/init.d# ./postgresql-8.1 start > Starting PostgreSQL 8.1 database server: main* Use of uninitialized value in > pattern match (m//) at /usr/share/postgresql-common/PgCommon.pm line 433. > Error: Could not create log file > failed! You need to report this to the Debian packager, not to us --- we don't know anything about the shell script they use. regards, tom lane ---(end of broadcast)--- TIP 4: Have you searched our list archives? http://archives.postgresql.org
