Re: [GENERAL] More details on Database corruption

From: Dimitri <dimitri(at)France(dot)Sun(dot)COM>
To: pgsql-general(at)postgreSQL(dot)org
Subject: Re: [GENERAL] More details on Database corruption
Date: 1998-08-13 16:45:01
Message-ID: 98081318574802.00469@dimitri
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

It seems to be the same for me...
But I can see "tasks" table after restarting of psql,
so it doesn't crash the data files.

What can be usefull is the messages in the server.log file:
Too Large Allocation Request ... File: mcxt.c Line: 232

I don't know the code of PG, but we can ask PG "gurus" ...
Dimitri

On Thu, 13 Aug 1998, you wrote:
>Hi,
>
>I managed to recreate a simple example that's crashing postgres. I am
>running on a DEC Alpha with Digital Unix Version 4.0d and Postgres
>3.2. I tried this example several times, on several databases and it
>crashes every time. We also re-built Postgres and still did not work.
>Here's the example. Can anybody please help?
>
>Thank you...
>George K.
>/***** INPUT FILE: hist.sql *******/
>
>drop table tasks;
>CREATE TABLE tasks (
>task INT4 NOT NULL,
>job INT4 NOT NULL,
>Version1 CHAR(6) DEFAULT '',
>Version2 CHAR(6) DEFAULT '',
>Version3 CHAR(6) DEFAULT '',
>Version4 CHAR(6) DEFAULT '',
>Version5 CHAR(6) DEFAULT ''
>);
>
>INSERT INTO tasks (task, job) VALUES (1, 1);
>select * from tasks;
>update tasks set version1='1',version2='2', version3='3', version4='4',
>version5='5' where task=1;
>select * from tasks;
>
>
>/****** OUTPUT FROM pgsql **********/
>test=> \i hist.sql
>drop table tasks;
>DROP
>CREATE TABLE tasks (
>task INT4 NOT NULL,
>job INT4 NOT NULL,
>Version1 CHAR(6) DEFAULT '',
>Version2 CHAR(6) DEFAULT '',
>Version3 CHAR(6) DEFAULT '',
>Version4 CHAR(6) DEFAULT '',
>Version5 CHAR(6) DEFAULT ''
>);
>CREATE
>
>INSERT INTO tasks (task, job) VALUES (1, 1);
>INSERT 4410388 1
>select * from tasks;
>task|job|version1|version2|version3|version4|version5
>----+---+--------+--------+--------+--------+--------
> 1| 1| | | | |
>(1 row)
>
>update tasks set version1='1',version2='2', version3='3', version4='4',
>version5='5' where task=1;
>UPDATE 1
>select * from tasks;
>FATAL: unrecognized data from the backend. It probably dumped core.
>FATAL: unrecognized data from the backend. It probably dumped core.
>
>EOF
>test=>
--
=====================================================
Dimitri KRAVTCHUK (dim) Sun Microsystems
Benchmark Engineer France
dimitri(at)France(dot)Sun(dot)COM
=====================================================

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Vadim Mikheev 1998-08-14 02:07:25 Re: [GENERAL] Unique key with nulls and copying databases across computers
Previous Message George Kousi 1998-08-13 15:59:25 More Details (cont.)

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1998-08-13 17:31:54 Re: [HACKERS] tuple return from function
Previous Message Tom Lane 1998-08-13 16:41:22 Re: [INTERFACES] Libpq problems (not)