* Alfred Perlstein <[EMAIL PROTECTED]> [000920 06:19] wrote:
> There's two tracebacks of crashed 7.0.2 backends at the end of this
> email.
Also, after this the database is extremely unstable, queries lock up
and the postgresql server (not OS) requires a complete restart and
vacuum analyze before
Alfred Perlstein <[EMAIL PROTECTED]> writes:
> I posted earlier this week about a table of ours getting corrupted
> after some time. The table looks like this:
> ...
> After a while we get this crash apparently, followed by crashes of any
> backend that scans this table, not updating this specifi
* Alfred Perlstein <[EMAIL PROTECTED]> [000920 06:19] wrote:
> There's two tracebacks of crashed 7.0.2 backends at the end of this
> email.
Sorry, a couple more things I should have included:
I'm running with a ~256 shared memory segment:
DAEMON=/usr/local/pgsql/bin/postmaster
DATA=/vol/amrd0/d
There's two tracebacks of crashed 7.0.2 backends at the end of this
email.
I posted earlier this week about a table of ours getting corrupted
after some time. The table looks like this:
details:
id | integer |
attr_type | varchar(32) |
attr_name | varchar(32) |
attr_vers |
