Re: [BUGS] initdb fail to execute
On Sunday, May 05, 2013 1:15 AM Jinu K J wrote: >Hi, >We are trying install postgresql 9.2.3 version for windows xp. >Below issue happen only for this particular PC. >Other windows XP installations are ok. >Here initdb command failed mentioning that , it is able to find postgres , but version mismatched. Can you please check is there any other version of postgres present in the machine? Regards, Hari babu.
Re: [BUGS] BUG #8137: Instalação aparece erro
On 06-05-2013 09:57, jvalssi...@gmail.com wrote: > Quando estou tentando instalar o postgres 8.2 no windows 2012 server aparece > esse erro. > > malformed permissions property langid > > Tem como corrigir e fazer essa instalação? > Valdomiro, *não* corrigimos versões descontinuadas. Além disso, a versão 8.2 foi descontinuada para Windows em dez/2011 (Windows Server 2012 foi lançado após esta data). Por que está querendo utilizar uma versão tão antiga? Considere utilizar uma versão suportada [1] pois a 8.2 contém bugs e limitações conhecidos. = Valdomiro, we *don't* fix deprecated versions. In addition, 8.2 was discontinued on dec/2011 (Windows Server 2012 was released *after* this date). Why do you want to use a deprecated version? Consider using a supported version [1] because 8.2 has known bugs and limitations. [1] http://www.postgresql.org/support/versioning -- Euler Taveira de Oliveira - Timbira http://www.timbira.com.br/ PostgreSQL: Consultoria, Desenvolvimento, Suporte 24x7 e Treinamento -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8138: No puedo ver los datos
On Mon, May 6, 2013 at 11:49 AM, wrote: > The following bug has been logged on the website: > > Bug reference: 8138 > Logged by: Jose Guerra > Email address: jgue...@solmovsa.com > PostgreSQL version: 9.2.4 > Operating system: Windows 7 Pro > Description: > > Espero me puedan ayudar, estoy tratando de traer datos de Postgres usando > PostgresSQL Unicode pero no me trae nada > > Esto no es una falla (al menos no es posible saberlo de la poca descripcion que estas dando), ademas que deberías reportar cualquier falla en inglés. Te estoy redirigiendo a pgsql-es-ay...@postgresql.org para que podemos a) hablar en español y b) determinar cual es realmente tu problema. This is not a bug (at least i can infer one from the little description you are giving), also you should report any bug in english. I'm redirecting you to pgsql-es-ay...@postgresql.org so we can a) speak spanish and b) determine what your problem is. -- Jaime Casanova www.2ndQuadrant.com Professional PostgreSQL: Soporte 24x7 y capacitación Phone: +593 4 5107566 Cell: +593 987171157 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8138: No puedo ver los datos
The following bug has been logged on the website: Bug reference: 8138 Logged by: Jose Guerra Email address: jgue...@solmovsa.com PostgreSQL version: 9.2.4 Operating system: Windows 7 Pro Description: Espero me puedan ayudar, estoy tratando de traer datos de Postgres usando PostgresSQL Unicode pero no me trae nada -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Inconsistency between TO_CHAR() and TO_NUMBER()
Am 06.05.2013 16:26, schrieb Tom Lane: Patryk Kordylewski writes: Hi, i have the following test-case: http://psql.privatepaste.com/b3b431851a Just for the record: this is a completely unacceptable method of submitting a bug report. After a month from now, when that paste has expired, nobody looking at the PG archives will have any way to find out what you were talking about. Even without the archival consideration, you've added an extra step to fetch the test case for anyone reading your mail. Having said that, though, this does look wrong ... regards, tom lane Hmpf, you're right. I'm sorry. Here is the test-case: PostgreSQL 9.2.4 (also tested on 9.1 and 8.2) ### WORKS SET lc_numeric TO 'en_US.UTF-8'; SET SELECT TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), TO_NUMBER(TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), 'FM99G999G999G999G999G999G999D000'); to_char | to_number -+--- 123,456,789.123 | 123456789.123 (1 row) ### DOES NOT WORK SET lc_numeric TO 'de_DE.UTF-8'; SET SELECT TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), TO_NUMBER(TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), 'FM99G999G999G999G999G999G999D000'); to_char | to_number -+--- 123.456.789,123 | 123.456 (1 row) ### FORMAT STRING WITHOUT FM PREFIX AND EXACT NUMBER OF DIGITS WORKS SELECT TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), TO_NUMBER(TO_CHAR(123456789.123, 'FM99G999G999G999G999G999G999D000'), '999G999G999D000'); to_char | to_number -+--- 123.456.789,123 | 123456789.123 (1 row) Thank you. Best regards, Patryk -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] Inconsistency between TO_CHAR() and TO_NUMBER()
Patryk Kordylewski writes: > Hi, > i have the following test-case: > http://psql.privatepaste.com/b3b431851a Just for the record: this is a completely unacceptable method of submitting a bug report. After a month from now, when that paste has expired, nobody looking at the PG archives will have any way to find out what you were talking about. Even without the archival consideration, you've added an extra step to fetch the test case for anyone reading your mail. Having said that, though, this does look wrong ... regards, tom lane -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] BUG #8137: Instalação aparece erro
The following bug has been logged on the website: Bug reference: 8137 Logged by: Valdomiro Email address: jvalssi...@gmail.com PostgreSQL version: Unsupported/Unknown Operating system: Windows 2012 Server Description: Prezados, Quando estou tentando instalar o postgres 8.2 no windows 2012 server aparece esse erro. malformed permissions property langid Tem como corrigir e fazer essa instalação? No Aguardo Valdomiro -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
[BUGS] Inconsistency between TO_CHAR() and TO_NUMBER()
Hi, i have the following test-case: http://psql.privatepaste.com/b3b431851a We want to convert a TO_CHAR() formated numeric back to numeric using TO_NUMBER() with the same format string. This does not work with a german locale. By removing the FM prefix and using the exact amount of digits in the format string for TO_NUMBER() it starts to work. Switching the locale back to en_US does work too. Is this a bug or am i missing something? Thanks! Best regards, Patryk -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
Re: [BUGS] BUG #8135: current_setting('DateStyle'); does not reflect User setting
On 05.05.2013 21:18, fr...@heuveltop.nl wrote:
PostgreSQL version: 9.1.8
Not that it makes any difference for this issue, but you should upgrade
to 9.1.9.
After
ALTER ROLE frank SET TimeZone = 'Europe/Amsterdam';
Where the TimeZone differs from the default timezone.
SELECT current_setting('TimeZone');
Gives the correct answer.
But this same doesn't work for DateStyle
ALTER ROLE frank SET DateStyle = 'SQL, DMY';
Where the DateStyle differs from the default DateStyle
SELECT current_setting('DateStyle');
Gives the system/database setting but not the user setting; while the
setting does have its effect on the output of date's and timestamps. This
might also effect other user settings, but I haven't found any yet.
Works for me. Are you sure the value isn't being overridden by a
per-database-and-role setting? You can use "select source from
pg_settings where name='DateStyle'" to check where the currently
effective value came from.
- Heikki
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
