Re: [HACKERS] postgres dies while doing vacuum analyze
Manuel Sugawara [EMAIL PROTECTED] writes: Tom Lane [EMAIL PROTECTED] writes: Manuel Sugawara [EMAIL PROTECTED] writes: [ vacuum analyze dies ] It is running on Redhat Linux 7.1 i686 with 2.4.2-2 kernel. Here is the back trace from gdb (gdb) bt #0 strcoll () at strcoll.c:229 We've heard reports before of strcoll() crashing on apparently valid input. It seems to be a Red Hat-specific problem; the three reports I have in my notes are from people running RH 7.0 (check the archives from 1/1/01, 1/24/01, 3/1/01 if you want to see the prior reports). It's possible that Postgres is doing something that confuses RH's locale library, but I dunno what. Since no other platform is reporting it, it could also be a plain old bug in that locale library. After a look into strcoll I found the bug. Attached is a tarball including a patch for strcoll, glibc.spec and an small program that shows the bug. Will do... what is the expected result of the testcase? It seems to work alright for me, but I'm running a slightly newer version than we have released yet... (glibc-2.2.3-11, look in rawhide). -- Trond Eivind Glomsrød Red Hat, Inc. ---(end of broadcast)--- TIP 3: 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
Re: [HACKERS] postgres dies while doing vacuum analyze
[EMAIL PROTECTED] (Trond Eivind =?iso-8859-1?q?Glomsr=F8d?=) writes: Will do... what is the expected result of the testcase? Given a sufficiently large discrepancy between the string lengths, a core dump is the likely result. Try increasing the 16k numbers if it doesn't crash for you. Good work, Manuel! I'm surprised this hasn't been found before, because you'd think it'd be biting lots of people ... regards, tom lane ---(end of broadcast)--- TIP 3: 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
Re: [HACKERS] postgres dies while doing vacuum analyze
On 16 Jun 2001, Manuel Sugawara wrote: [EMAIL PROTECTED] (Trond Eivind Glomsrød) writes: [...] OK, this works with my system - no coredump, correct results. I'll take a look at the glibc sources to verify that, but it looks like this was fixed by [EMAIL PROTECTED] and included in glibc 2.2.3: https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=36539 yes, is already fixed on glibc-2.2.3. It's safe to install this version on my 7.1 systems The 2.2.3-11 should be safe, we would be very interested to hear othwerwise. -- Trond Eivind Glomsrød Red Hat, Inc. ---(end of broadcast)--- TIP 3: 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
Re: [HACKERS] postgres dies while doing vacuum analyze
Tom Lane [EMAIL PROTECTED] writes: Manuel Sugawara [EMAIL PROTECTED] writes: [ vacuum analyze dies ] It is running on Redhat Linux 7.1 i686 with 2.4.2-2 kernel. Here is the back trace from gdb (gdb) bt #0 strcoll () at strcoll.c:229 We've heard reports before of strcoll() crashing on apparently valid input. We haven't AFAIK, but would be very interested if it can be reproduced. -- Trond Eivind Glomsrød Red Hat, Inc. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://www.postgresql.org/search.mpl
Re: [HACKERS] postgres dies while doing vacuum analyze
Manuel Sugawara [EMAIL PROTECTED] writes: [ vacuum analyze dies ] It is running on Redhat Linux 7.1 i686 with 2.4.2-2 kernel. Here is the back trace from gdb (gdb) bt #0 strcoll () at strcoll.c:229 We've heard reports before of strcoll() crashing on apparently valid input. It seems to be a Red Hat-specific problem; the three reports I have in my notes are from people running RH 7.0 (check the archives from 1/1/01, 1/24/01, 3/1/01 if you want to see the prior reports). It's possible that Postgres is doing something that confuses RH's locale library, but I dunno what. Since no other platform is reporting it, it could also be a plain old bug in that locale library. We need some RH-er to burrow in with a debugger and figure out what's going wrong. The previous reporters don't seem to have done anything; are you the man to fix it? regards, tom lane ---(end of broadcast)--- TIP 3: 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
