Re: [BUGS] BUG #6452: psql: can't change client encoding from the command line

2012-02-14 Thread Heikki Linnakangas
On 11.02.2012 20:02, felix.gerzag...@gmail.com wrote: Using the command line, I can't change the client encoding, but I can change it using the "\encoding" command : C:\>psql --variable=ENCODING=UTF8 could not find a "psql" to execute could not find a "psql" to execute psql (9.1.2) WARNING: Cons

[BUGS] BUG #6457: Regexp not processing word (with special characters on ends) correctly (UTF-8)

2012-02-14 Thread albert . cieszkowski
The following bug has been logged on the website: Bug reference: 6457 Logged by: Albert Cieszkowski Email address: albert.cieszkow...@cc.com.pl PostgreSQL version: 9.0.6 Operating system: CentOS 5.x Description: OS, base and client encoding UTF-8: peimp=> select 'Świ

Re: [BUGS] BUG #6457: Regexp not processing word (with special characters on ends) correctly (UTF-8)

2012-02-14 Thread Tom Lane
albert.cieszkow...@cc.com.pl writes: > OS, base and client encoding UTF-8: What's your lc_collate/lc_ctype settings? regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref

Re: [BUGS] BUG #6457: Regexp not processing word (with special characters on ends) correctly (UTF-8)

2012-02-14 Thread Albert Cieszkowski
Hello Tom, Every lc_x value is pl_PL.UTF8 (corresponding to the word's language). Database was created with --locale=pl_PL.UTF8. OS (CentOS 5.x) uses: en_US.UTF-8 Best regards, Albert Cieszkowski W dniu 2012-02-14 16:27, Tom Lane pisze:

[BUGS] BUG #6458: LIKE different to =

2012-02-14 Thread hlemcke
The following bug has been logged on the website: Bug reference: 6458 Logged by: Hajo Email address: hlem...@web.de PostgreSQL version: 9.1.2 Operating system: Windows XP Description: colname = 'value' returns true but colname LIKE 'value' returns false. -- Sent vi

Re: [BUGS] BUG #6458: LIKE different to =

2012-02-14 Thread Kevin Grittner
wrote: > colname = 'value' returns true but > colname LIKE 'value' returns false. Is the colname of type char(n) or does it contain trailing spaces? -Kevin -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpr

Re: [BUGS] BUG #6457: Regexp not processing word (with special characters on ends) correctly (UTF-8)

2012-02-14 Thread Tom Lane
albert.cieszkow...@cc.com.pl writes: > peimp=> select 'Świnoujście' ~* '\mŚwinoujście\M'; > ?column? > -- > f > (1 row) Oh, I see the reason for this: the code in cclass() in regc_locale.c doesn't go further up than U+00FF, so no codes above that will be thought to be letters (or mem

[BUGS] BUG #6459: logging_collector=off but log_filename set inhibits logoutpu

2012-02-14 Thread calestyo
The following bug has been logged on the website: Bug reference: 6459 Logged by: Christoph Anton Mitterer Email address: cales...@scientia.net PostgreSQL version: 9.1.1 Operating system: All Description: Hi. http://www.postgresql.org/docs/9.1/static/runtime-config-lo

Re: [BUGS] BUG #6459: logging_collector=off but log_filename set inhibits logoutpu

2012-02-14 Thread Tom Lane
cales...@scientia.net writes: > http://www.postgresql.org/docs/9.1/static/runtime-config-logging.html > claims that log_filename is only used when logging_collector is enabled. That is a true statement, as can easily be proven by looking at the source code: nothing except syslogger.c pays any atte

Re: [BUGS] BUG #6412: psql & fe-connect truncate passwords

2012-02-14 Thread Andy Grimm
On Sat, Jan 28, 2012 at 7:47 PM, Euler Taveira de Oliveira wrote: > On 28-01-2012 18:55, Andy Grimm wrote: >> It's not uniform between the client and the server, though. >> > The server doesn't impose a hard limit for password length and AFAICS it > should not because we aim for backward compatibi