Re: [BUGS] 7.2.1 backend crash (convert_string_datum, locale)
[EMAIL PROTECTED] (Andrew Sullivan) writes: > On Thu, Jul 11, 2002 at 11:15:42PM -0400, Tom Lane wrote: > > Mats Lofkvist <[EMAIL PROTECTED]> writes: > > > When testing postgres 7.2.1 on a sparc/solaris8 box with > > > --enable-locale --enable-multibyte I get a crash in > > > convert_string_datum. > > > > This smells like a problem that we chased down awhile back, that > > snprintf on Solaris is broken (it will write past the end of the > > specified buffer length, thus corrupting adjacent data). > > It does indeed. This was only the 64-bit library, though, or at > least as far as we were able to tell. And I wasn't able to turn up > any evidence that it happened on Solaris 8. But it might. We don't > use 8, at least not yet. > > > Andrew, I think that was your test case we found it on. Do you > > recall if a fix is available from Sun? > > Not as far as I know, at least for 7. Come to think of it, I now > _do_ recall seeing something in my various Google wanderings which > suggested that there is a fix in one of the patch packages for > Solaris 8 (which suggests the buggy library is in the basic Solaris 8 > install). I dimly recall some mention of incompatibility between it > and some other patchlevel, as well, so it might require some digging. > (Given that it's really a bounds mistake in a system library, you'd > think that it'd be easier to find more information about it; I > actually learned almost everything I know about the problem from, > IIRC, the autoconf web pages, so I'd not expect a cursory search of > Sun's site to turn anything up.) > > In the FAQ_Solaris, there is a suggestion to use the substitute > function included in the Postgres tree (which is what you suggested, > Tom, and what I did), as well as instructions on how to do it. It > definitely works for me on Solaris 7. Might be worth trying on 8 as > well. If so, the FAQ should be updated so as not to limit the > discussion to Solaris 7 and earlier. I didn't get it to work with the stuff in FAQ_Solaris (can't guarantee I really got snprintf substituted though, just followed the instructions and recompiled). Removing --enable-multibyte didn't help either. Without neither --enable-locale or --enable-multibyte it seems to work, but as I had to create a new database when removing locale any problems local to the first database are not seen anymore. Is postgres 8-bit clean without locale support enabled? (I don't care about sort orders and such, only need to read/write 8-bit chars via jdbc). _ Mats Lofkvist [EMAIL PROTECTED] ---(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: [BUGS] 7.2.1 backend crash (convert_string_datum, locale)
Mats Lofkvist <[EMAIL PROTECTED]> writes: > Without neither --enable-locale or --enable-multibyte it > seems to work, but as I had to create a new database when > removing locale any problems local to the first database > are not seen anymore. Hm. If the database is already corrupt then simply recompiling a corrected binary isn't going to magically make things perfect. Maybe you should retry the snprintf patch and/or --enable-multibyte using fresh databases. > Is postgres 8-bit clean without locale support enabled? > (I don't care about sort orders and such, only need to > read/write 8-bit chars via jdbc). In that case you don't really need locale, no. Not sure about whether you need multibyte; does JDBC expect Unicode support? regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/users-lounge/docs/faq.html
[BUGS] Unable to install postgres on Mips platform.
Hello: I am trying to install postgres 7.1 version on a Mips platform running Linux (2.4.17sb20020611 version). The postgres source is compiled with Montevista cross compiler (gcc version 3.0.1) for the mips platform. The problem I am having is that when I call initdb, the postgres dies because of the following error: Program received signal SIGSEGV, Segmentation fault. This problem occurs in file postgresql-7.1.3/src/backend/access/heap/heapam.c (line 1808) where it is trying to invoke log_heap_update function. When I try to step into the function log_heap_update function, the program control goes into memcpy and I get SIGSEGV fault. Any help in resolving this problem is greatly appreciated. Thanks very much. Regards, Niranjan. ---(end of broadcast)--- TIP 6: Have you searched our list archives? http://archives.postgresql.org
Re: [BUGS] Unable to install postgres on Mips platform.
Please try 7.2.1 from ftp.postgresql.org. --- Niranjan Shivaratri wrote: > > Hello: > > I am trying to install postgres 7.1 version on a Mips platform running Linux >(2.4.17sb20020611 version). > The postgres source is compiled with Montevista cross compiler (gcc version 3.0.1) >for the mips platform. > > The problem I am having is that when I call initdb, the postgres dies because of the >following error: > > Program received signal SIGSEGV, Segmentation fault. > > This problem occurs in file postgresql-7.1.3/src/backend/access/heap/heapam.c (line >1808) > where it is trying to invoke log_heap_update function. > > When I try to step into the function log_heap_update function, the program control >goes into > memcpy and I get SIGSEGV fault. > > Any help in resolving this problem is greatly appreciated. > > Thanks very much. > > Regards, > Niranjan. > > > ---(end of broadcast)--- > TIP 6: Have you searched our list archives? > > http://archives.postgresql.org > -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 853-3000 + If your life is a hard drive, | 830 Blythe Avenue + Christ can be your backup.| Drexel Hill, Pennsylvania 19026 ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
