[GENERAL] psql Segmentation fault

Since we converted to PG8, we've been experiencing segfaults when the psql client exits. It doesn't have any real effect on things... or it hasn't until now. RHEL4 i686 - PostgresQL 8.2.4 (non-redhat) -bash-3.00$ psql -n Welcome to psql 8.2.4, the PostgreSQL interactive terminal. Type:

Re: [GENERAL] psql Segmentation fault

Tom Lane wrote: Robert Landrum [EMAIL PROTECTED] writes: Since we converted to PG8, we've been experiencing segfaults when the psql client exits. Hmm. We have heard that reported on OS X because of a bug in Apple's version of libedit, but not on any flavor of Linux. Your tests seem

[GENERAL] Indexing Hostnames with tsearch2 and fti.c

We're currently using the old fti.c code for searching our database. It's indexing a mixed bag of hostnames, employee names, ticket subjects, and the like. We hacked it to make it work correctly for hostnames, ignoring whitespace and periods as word boundaries. Since were moving to 8.2, we

[GENERAL] Stored Proc Problem

I'm writing a stored procedure that will execute as a trigger. Arguments being passed to the procedure are field names. My goal is to convert those field names into the field values. However, I've not been successful. I thought that the following should have worked. EXECUTE ''field_val :=

[GENERAL] GiST Support in 8.1

We're migrating from a 7.4 (Linux AS2.1) system to an 8.1.5 (Linux RHEL4 X64) system. In 7.4, we used tsearch (txtidx fields) on some tables. When we attempt to load the indexes for those fields in 8.1.5, we get a strange SEGV. \d historyticket [cut] short_summary_idx | txtidx

Re: [GENERAL] GiST Support in 8.1

Tom Lane wrote: 8.1.5 isn't exactly the latest, but I don't see any relevant-looking gist or tsearch2 fixes in the CVS history since then, so this may still be a live bug. As it turns out, tsearch is considered obsolete, and I should be using tsearch2. Talk about being behind the times...