Re: [BUGS] select to_number('1,000', '999,999');
On Mon, 2004-11-22 at 11:08 -0500, Tom Lane wrote: > Stephan Szabo <[EMAIL PROTECTED]> writes: > > No, but I think you're supposed to use FM in such cases. > > > > select to_number(1000, 'FM999,999'); > > Good point --- I had forgot about FM. In that case there *is* a bug > here, but I'm not sure if it's with to_char or to_number: > > regression=# select to_number(to_char(1000, 'FM999,999'),'FM999,999'); > to_number > --- > 1000 > (1 row) > > regression=# select to_number(to_char(1000, '999,999'),'999,999'); > to_number > --- >100 > (1 row) It's to_number() bug. I'm not sure if now (before release) is good time to fix it. The code of to_number() is not stable for changes and maybe we can fix this bug add some other new... I already work on new version for next release. It will use unit-tests -- I hope it will prevent a lot of bugs like this. > Whatever your opinion is about the behavior of the non-FM format, surely > to_char and to_number should be inverses. Yes. Karel -- Karel Zak http://home.zf.jcu.cz/~zakkr ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1320: 7.3.8 server RPM has file error
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Tue, 23 Nov 2004, Simon Riggs wrote: I've just realised that you *have* made a change to the 7.3.8 RPMs for Fedore Core 1...you've updated the readme. Referring to the readme...My problem was the RPMs didn't install, not that I couldn't get them to run. AFAICS the 7.3.8 RPMs for FC1 are just not operable. Any change in sight? (This setup is not for *me*) I *currently* do not have a FC1 for a test :-( I've tested FC1 RPMs on FC3, they worked, but it's not enough... If you can, could you please rebuild ftp://ftp6.tr.postgresql.org/postgresql/binary/v7.3.8/srpms/fedora/fedora-core-3/postgresql-7.3.8-3PGDG.src.rpm (or from any mirror near you) on FC1 and look what's happening? Thanks, Regards, - -- Devrim GUNDUZ devrim~gunduz.orgdevrim.gunduz~linux.org.tr http://www.tdmsoft.com http://www.gunduz.org -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.1 (GNU/Linux) iD8DBQFBovzDtl86P3SPfQ4RAqAjAKCYcwOZVrugdt3RNa7MpoO9beVbKQCgz2Xd g1wai7OAbaUJC5VhmkVHh9Y= =ucOv -END PGP SIGNATURE- ---(end of broadcast)--- TIP 7: don't forget to increase your free space map settings
Re: [BUGS] Getting weird results with unicode table...
"David B" <[EMAIL PROTECTED]> writes: > Two possible bugs. > #1 Loading unicode data. I'm thinking that the dump file probably doesn't set client_encoding, or if it does, sets it to the wrong thing. Is the data in the dump file actually UTF8, or is it in some other encoding? > select substring ( lower(title), 1, 1), count(*) > from album > where lower(title) > 'a%' and lower(title) <= 'e%' > group by substring ( lower(title), 1, 1) ; > Should get counts for 'a', 'b', 'c', 'd', 'e'. ... plus any other characters that the current locale chooses to sort between 'a' and 'e'. In particular I'd expect to see accented 'a' and/or accented 'e' sort that way. regards, tom lane ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] select to_number('1,000', '999,999');
Hi Karel, On Tue, Nov 23, 2004 at 09:39:21 +0100, Karel Zak wrote: > It's to_number() bug. I'm not sure if now (before release) is good time > to fix it. The code of to_number() is not stable for changes and maybe > we can fix this bug add some other new... I have the workaround with 'FM' so it is not urgent for me... > I already work on new version for next release. It will use > unit-tests -- I hope it will prevent a lot of bugs like this. Sounds great, thank you. Cheers David -- David Schweikert| phone: +41 44 632 7019 System manager ISG.EE | walk: ETH Zentrum, ETL F24.1 ETH Zurich, Switzerland | web: http://people.ee.ethz.ch/dws ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] Hi
Siva, yes, this ist the correct version. Regards, Harald On Mon, 22 Nov 2004 19:47:55 +0530, Siva Ganesh <[EMAIL PROTECTED]> wrote: > Hi > > I wanted to involve in Postgres beta testing. I want to the test the Windows > Beta version. > > I have downloaded the below > > ftp://ftp4.ar.postgresql.org/pub/mirrors/postgresql/win32/postgresql-8.0.0-beta4.zip > > Is this the right version for Beta testing? I am consfused > > Regards > > Siva Ganesh > > _ > Instant personal loans. Celebrate this season with your family. > http://acm.bridgeovertw.com/hdfc/pl/landingpage/sep04/index.htm?sitecode=611|395 > Apply. > > ---(end of broadcast)--- > TIP 5: Have you checked our extensive FAQ? > > http://www.postgresql.org/docs/faqs/FAQ.html > -- GHUM Harald Massa Harald Armin Massa Reinsburgstraße 202b 70197 Stuttgart 0173/9409607 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1320: 7.3.8 server RPM has file error
On Tue, 2004-11-23 at 09:02, Devrim GUNDUZ wrote: > On Tue, 23 Nov 2004, Simon Riggs wrote: > > > I've just realised that you *have* made a change to the 7.3.8 RPMs for > > Fedore Core 1...you've updated the readme. > > > > Referring to the readme...My problem was the RPMs didn't install, not > > that I couldn't get them to run. > > > > AFAICS the 7.3.8 RPMs for FC1 are just not operable. > > > > Any change in sight? (This setup is not for *me*) > > I *currently* do not have a FC1 for a test :-( I've tested FC1 RPMs on > FC3, they worked, but it's not enough... > > If you can, could you please rebuild > > ftp://ftp6.tr.postgresql.org/postgresql/binary/v7.3.8/srpms/fedora/fedora-core-3/postgresql-7.3.8-3PGDG.src.rpm > (or from any mirror near you) > > on FC1 and look what's happening? > A! Happily, I've not done that before. I either build from source, if people let me, or use the supplied/keyed RPMs. Withdrawing ungracefully...it's not anything I'd want to do right now, since I would also have to support that for the community as a whole. That would be a commitment I can't make right now. Again: I do appreciate your own efforts in that area. -- Best Regards, Simon Riggs ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
[BUGS] 8.0.0beta5 fails "make check" on Solaris9/i386
Hello, "make check" failed on my system. See the last line below and the "/./" in the pathname. Ask if you want more information then I have included below. I'm not subscribbed to the list. Send direct e-mail. Thanks for all the hard work. I'm using 7.4 in daily production on same system. wi792:~/postgresql-8.0.0beta5>uname -a SunOS wi792.aero.org 5.9 Generic_117172-11 i86pc i386 i86pc Solaris wi792:~/postgresql-8.0.0beta5/doc>gcc --version gcc (GCC) 3.3.2 wi792:~/postgresql-8.0.0beta5/doc>make --version GNU Make version 3.78.1, by Richard Stallman and Roland McGrath. Built for i386-pc-solaris2.8 wi792:~/postgresql-8.0.0beta5>make check == creating temporary installation== == initializing database system == pg_regress: initdb failed Examine ./log/initdb.log for the reason. make[2]: *** [check] Error 2 make[2]: Leaving directory `/home/alberts/postgresql-8.0.0beta5/src/test/regress' make[1]: *** [check] Error 2 make[1]: Leaving directory `/home/alberts/postgresql-8.0.0beta5/src/test' make: *** [check] Error 2 wi792:~/postgresql-8.0.0beta5> cat /home/alberts/postgresql-8.0.0beta5/src/test/regress/log/initdb.log Running in noclean mode. Mistakes will not be cleaned up. The files belonging to this database system will be owned by user "alberts". This user must also own the server process. The database cluster will be initialized with locale C. creating directory /home/alberts/postgresql-8.0.0beta5/src/test/regress/./tmp_check/data ... initdb: failed wi792:~/postgresql-8.0.0beta5> = Chris Albertson Home: 310-376-1029 [EMAIL PROTECTED] Cell: 310-990-7550 Office: 310-336-5189 [EMAIL PROTECTED] KG6OMK __ Do you Yahoo!? Meet the all-new My Yahoo! - Try it today! http://my.yahoo.com ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] 8.0.0beta5 fails "make check" on Solaris9/i386
Chris Albertson <[EMAIL PROTECTED]> writes: > creating directory > /home/alberts/postgresql-8.0.0beta5/src/test/regress/./tmp_check/data > ... initdb: failed Now that I look at it, the new improved incarnation of initdb seems prone to say no more than that after a lot of different errors :-(. But the question for you is why it couldn't create that directory. Permissions problem maybe? regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
