Re: [BUGS] An statement causes postmaster to die

2001-04-22 Thread Sean Kelly
On Sun, 22 Apr 2001, [EMAIL PROTECTED] wrote: > Can't tell much of anything from this. Can you provide a gdb backtrace > from the corefile that the failed backend presumably left? It should be > in $PGDATA/base/isp/core. Please ignore my last mail, I've found some documentation. Star

Re: [BUGS] An statement causes postmaster to die

2001-04-22 Thread Sean Kelly
On Sun, 22 Apr 2001, [EMAIL PROTECTED] wrote: > Can't tell much of anything from this. Can you provide a gdb backtrace > from the corefile that the failed backend presumably left? It should be > in $PGDATA/base/isp/core. I have the core file but cannot remember how to make a backtrace.

[BUGS] "select ... where field like lower('%text%')" fails

2001-03-07 Thread Sean Kelly
Hello, I was trying to send the following bug report from the web page but it kept timing out. I hope this is the only time it arrives on the list... I am trying to search a varchar(x) field with a query like: select ... where field like lower('%someText%')

Re: [BUGS] backend closed the channel unexpectedly?!?

2000-11-09 Thread Sean Kelly
LE referencing MASTER_TABLE. Listen to Tom ... he knows his stuff ;) -- Sean Kelly <[EMAIL PROTECTED]> "If 99% is good enough, then gravity will not work for 14 minutes every day."

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-30 Thread Sean Kelly
aming of a table involving foreign keys. I renamed the table back to what it was, dropped it, and then recreated the new one with new foreign keys. Thanks, -- Sean Kelly <[EMAIL PROTECTED]> "If 99% is good enough, then gravity will not work for 14 minutes every day."

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-26 Thread Sean Kelly
On Thu, 26 Oct 2000 11:27:22 -0400, Tom Lane said: > Sean Kelly <[EMAIL PROTECTED]> writes: > > (gdb) bt > > #0 0x8115eb2 in ri_BuildQueryKeyFull () > > #1 0x8115dc2 in RI_FKey_keyequal_upd () > > #2 0x8096d7c in DeferredTriggerSaveEvent () > > Hm

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-26 Thread Sean Kelly
uery () #11 0x80eaeec in PostgresMain () #12 0x80d565a in DoBackend () #13 0x80d523a in BackendStartup () #14 0x80d45ee in ServerLoop () #15 0x80d407c in PostmasterMain () #16 0x80ab115 in main () #17 0x400f9577 in __libc_start_main () from /lib/libc.so.6 (gdb) quit There we go :) Thanks,

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-26 Thread Sean Kelly
; > problem > > Uh, whoever told you that? Signal 11 is SIGSEGV on most Unixen, > and that just means the program tried to dereference an invalid > pointer. Almost certainly, we're looking at some software bug > here, not a hardware failure. One example can b

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-25 Thread Sean Kelly
any other suggestions? With respect to GCC errors, '11' normally indicates a hardware problem - could this be the case? One of the machines I tested it on was brand new hardware... Thanks, -- Sean Kelly <[EMAIL PROTECTED]> "If 99% is good enough, then gravity will not work for 14 minutes every day."

Re: [BUGS] Updating multiple bool values crashes backend

2000-10-25 Thread Sean Kelly
handling writing 5 The Data Base System is starting up /usr/local/postgres/bin/postmaster: ServerLoop: handling writing 5 DEBUG: Data Base System is in production state at Wed Oct 25 13:15:35 2000 proc_exit(0) shmem_exit(0) exit(0) /usr/local/postgres/bin/postmaster: reaping dead processe

Re: [BUGS] How to connect to a remote database

2000-09-10 Thread Sean Kelly
You'll probably have to edit /path/to/pgsql/lib/pg_hba.conf on the remote machine to get permission. Thanks, -- Sean Kelly <[EMAIL PROTECTED]> "The best way to predict the future is to invent it" - Alan Kay

[BUGS] ";" no longer allowed to terminate a command beginning with "\"

2000-06-24 Thread Sean Kelly
th a semi-colon, and I also know that the backslashed commands are _not_ SQL statements. In my case, I know I am used to ending almost everything I write with a semicolon but was just wondering whether this was a planned change to the "psql" application. Thanks for your time,

Re: [BUGS] More "IpcMemoryCreate: shmget failed" errors

2000-06-17 Thread Sean Kelly
e: > Hi ! > And your OS ? > Sorry, I did't followed your story. If you tell me, I can help you. [Covered above] Thanks to all who replied, your help is greatly appreciated. -- Sean Kelly <[EMAIL PROTECTED]> "The best way to predict the future is to invent it" - Alan Kay

[BUGS] More "IpcMemoryCreate: shmget failed" errors

2000-06-16 Thread Sean Kelly
a way that v7 could check for these old segments from v6 and remove them? Is this even the problem here? Any other ways to clear these suspected old segments at all? Thanks for your time, -- Sean Kelly <[EMAIL PROTECTED]> "The best way to predict the future is to invent it" - Alan Kay

[BUGS] "IpcMemoryCreate: shmget failed" on 2.0.38 (was Re: Bug?)

2000-06-08 Thread Sean Kelly
On Wed, 7 Jun 2000, Tom Lane wrote: > > IpcMemoryCreate: shmget failed (Invalid argument) key=5432010, size=144, >permission=700 > > My kernel has been compiled with "System V IPC" selected. > > PostgreSQL 6.5.3 has been compiled and ran on this system. > > Hmm, maybe there are old shme

[BUGS] Bug?

2000-06-07 Thread Sean Kelly
POSTGRESQL BUG REPORT TEMPLATE Your name : Sean Kelly Your email address : [EMAIL PROTECTED