Here is a bug I found. It kind of worries me.
-- cary
============================================================================
POSTGRESQL BUG REPORT TEMPLATE
============================================================================
Your name : Cary O'Brien
Your email address : [EMAIL PROTECTED]
System Configuration
---------------------
Architecture (example: Intel Pentium) : Intel Pentium
Operating System (example: Linux 2.0.26 ELF) : Linux 2.0.34/
PostgreSQL version (example: PostgreSQL-6.5.2): PostgreSQL-6.5.2
Compiler used (example: gcc 2.8.0) : GCC 2.7.2.3
Please enter a FULL description of your problem:
------------------------------------------------
Executing a "select ... for update" corrupts index files.
Note that Applixware Builder seems to execute "select ... for update"
automatically. This is how the problem was discovered.
Please describe a way to repeat the problem. Please try to provide a
concise reproducible example, if at all possible:
----------------------------------------------------------------------
Fresh rebuild and install...
[cary@zeos cary]$ createdb foo
[cary@zeos cary]$ psql foo
Welcome to the POSTGRESQL interactive sql monitor:
Please read the file COPYRIGHT for copyright terms of POSTGRESQL
[PostgreSQL 6.5.2 on i486-pc-linux-gnu, compiled by gcc 2.7.2.3]
type \? for help on slash commands
type \q to quit
type \g or terminate with semicolon to execute query
You are currently connected to the database: foo
foo=> select * from pg_class for update;
[snip data]
foo=>\q
Connection to database 'foo' failed.
pqReadData() -- backend closed the channel unexpectedly.
This probably means the backend terminated abnormally
before or while processing the request.
Note...
The backend gets a sigsegv after opening one of the index
files for pg_class.
If you know how this problem might be fixed, list the solution below:
---------------------------------------------------------------------
