Fw: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table
I tried to reply to you but that doesn't work. So I try it through here.. Yours, Aarjan - Original Message - From: aarjan langereis To: Tom Lane Sent: Saturday, December 20, 2003 3:17 PM Subject: Fw: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table Did you find time to read my email? I hope you will reply sone. Yours, Aarjan - Original Message - From: aarjan langereis To: [EMAIL PROTECTED] Sent: Friday, December 19, 2003 9:39 AM Subject: Re: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table How do I get a "debugger backtrace" ?Selecting all data from the tables involved, does that also include a 'count(*)', if so, they work:stats=# select count(*) from blocks; count- 3194409(1 row)stats=# select count(*) from hosts; count--- 205(1 row)stats=#Yours,Aarjan- Original Message - From: "Tom Lane" <[EMAIL PROTECTED]>To: <[EMAIL PROTECTED]>Cc: "PostgreSQL Bugs List" <[EMAIL PROTECTED]>Sent: Friday, December 19, 2003 4:41 AMSubject: Re: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table > "PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes:> > I tried to create a temp table and got my back-end restarting because of a signal 11.> > Hmm. Can you get a debugger backtrace from the core dump?> > > It seems to me, and please correct me if Iâ?Tm wrong, that there is a limit to the size that a join can handle.> > No (and certainly not on a measly 3-million-row case). This could be a> data corruption problem, or something more subtle, but it's not that.> > One way of testing the data-corruption theory is to see if you can> select all the data from the tables involved, without any join.> > regards, tom lane>
Re: [BUGS] BUG #1015: Got a signal 11 while trying to create a temp table
"aarjan langereis" <[EMAIL PROTECTED]> writes: > How do I get a "debugger backtrace" ? Find the "core" file left by the crashed backend --- it should be in $PGDATA/base/yourdbnumber/core and have a file date equal to the time of the crash. If you don't find one, it's likely that the postmaster was started under "ulimit -c 0" which prevents core dumps. Restart the postmaster under "ulimit -c unlimited" and reproduce the crash. Once you have the core file, do $ gdb /path/to/postgres-executable /path/to/core-file gdb> bt gdb> quit If bt just produces a list of numbers without any names, it's not going to be helpful. In that case you need to rebuild Postgres with debugging symbols and start over. There is more info in the archives. > Selecting all data from the tables involved, does that also include a 'coun= > t(*)', if so, they work: Mmm, that really only proves that the page headers and tuple headers are OK, not that there is not data corruption within some row, because COUNT(*) won't try to extract any field values from any rows. I'd suggest a SELECT * or COPY TO FILE operation to check whether there is any data corruption. regards, tom lane ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
Re: [BUGS] BUG #1021: IDENT authorization doesn't work
"PostgreSQL Bugs List" <[EMAIL PROTECTED]> writes: > PostgreSQL version: 7.4 > Operating system: FreeBSD 4.9-STABLE > Description:IDENT authorization doesn't work Fixed for 7.4.1. Thanks for the report. 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
[BUGS] can not configure --enable-thread-safety
I'm on Mac OS X 10.3.2 gcc --version gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build 1495) cannot ./configure --enable-thread-safety I don't know what to send to youse guys... checking for pthread.h... yes configure: error: Cannot enable threads on your platform. Please report your platform threading info to the PostgreSQL mailing lists so it can be added to the next release. Report all compile flags, link flags, functions, or libraries required for threading support. See the comment at the top of src/port/thread.c for more information. I don't know where to look for the 'threading info' to report it back to you. I would be happy to look if someone could help me. Ted __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ---(end of broadcast)--- TIP 4: Don't 'kill -9' the postmaster
[BUGS] make check and OSX
I seem to be missing something on Mac OSX. ./configure --with-rendezvous make All of PostgreSQL successfully made. Ready to install. beautiful... so I tried make check [symcom:~/software/postgresql-7.4] postgres% make check All of PostgreSQL successfully made. Ready to install. make -C src/test check make: *** src/test: No such file or directory. Stop. make: *** [check] Error 2 I don't get it... am I not understanding something? I did the 'make check' as user postgres BTW, I did a 'make install' and the installation appears to be working fine. I would like to run the tests. Ted __ Do you Yahoo!? New Yahoo! Photos - easier uploading and sharing. http://photos.yahoo.com/ ---(end of broadcast)--- TIP 2: you can get off all lists at once with the unregister command (send "unregister YourEmailAddressHere" to [EMAIL PROTECTED])
Re: [BUGS] make check and OSX
Theodore Petrosky <[EMAIL PROTECTED]> writes: > I seem to be missing something on Mac OSX. > [symcom:~/software/postgresql-7.4] postgres% make > check > All of PostgreSQL successfully made. Ready to install. > make -C src/test check > make: *** src/test: No such file or directory. Stop. I can't duplicate this on either OS X 10.2.6 or 10.3 (beta). "make check" at top level works fine for me. regards, tom lane ---(end of broadcast)--- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html
Re: [BUGS] can not configure --enable-thread-safety
Theodore Petrosky wrote: > > I'm on Mac OS X 10.3.2 > gcc --version > gcc (GCC) 3.3 20030304 (Apple Computer, Inc. build > 1495) > > cannot ./configure --enable-thread-safety > > I don't know what to send to youse guys... > > checking for pthread.h... yes > configure: error: > Cannot enable threads on your platform. > Please report your platform threading info to the > PostgreSQL mailing lists so it can be added to the > next release. Report all compile flags, link flags, > functions, or libraries required for threading > support. > See the comment at the top of src/port/thread.c for > more information. > > > I don't know where to look for the 'threading info' to > report it back to you. I would be happy to look if > someone could help me. Not sure. You usually need to ask our questions to someone who is familiar with how to enable threading on your platform. -- Bruce Momjian| http://candle.pha.pa.us [EMAIL PROTECTED] | (610) 359-1001 + If your life is a hard drive, | 13 Roberts Road + Christ can be your backup.| Newtown Square, Pennsylvania 19073 ---(end of broadcast)--- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]