Re: [HACKERS] Postgres still dying on insert

On Mon, 27 Apr 1998, Michael Richards wrote:

> I have tried almost everything I can think of, put postgres keepy dying.
> I am running on a FreeBSD 2.2.5 system. It was complaining about not
> enough shared memory. I bumped the shared mem to 16mb (the system has 128)
> now it doesn't complain, it just dumps core.
> The numbers are different this time, but today, the command I am trying to
> execute is:
> INSERT INTO word_detail VALUES (131730,18596,1)
> now word_detail is:
> | word_id                          | int4               | 4 |
> | url_id                           | int4               | 4 |
> | word_count                       | int2               | 2 |
>
> and it has non-unique indexes on word_id and url_id
> sc=> select count(*) from word_detail;
> Field| Value
> -- RECORD 0 --
> count| 637466
>
> There is quite a bit of data here as well...
> sc=> INSERT INTO word_detail VALUES (131730,18596,1);
> PQexec() -- Request was sent to backend, but backend closed the channel
> before responding.
>         This probably means the backend terminated abnormally before or
> while processing the request.

    When this crash happens, do you restart postmaster itself?  If so,
will that INSERT work right afterwards?

    If not, what happens if you create a temporary table with the same
'schema' and insert that record?  Does that work?

    If not, what happens if you go to 'int8'?

>

Marc G. Fournier
Systems Administrator @ hub.org
primary: scrappy@hub.org           secondary: scrappy@{freebsd|postgresql}.org