Re: BUG #4296: Server crashes by restoring database

From: Michał Szeląg <msz(at)szel(dot)pl>
To: pgsql-bugs(at)postgresql(dot)org
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: BUG #4296: Server crashes by restoring database
Date: 2008-07-15 07:43:35
Message-ID: 200807150943.35846.msz@szel.pl
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Dnia poniedziałek, 14 lipca 2008, Tom Lane napisał:
> =?iso-8859-2?q?Micha=B3_Szel=B1g?= <msz(at)szel(dot)pl> writes:
> > the crash occurs by this command in my dump:
> >
> > COPY users_history (users_history_id, users_id, uh_date,
> > uh_php_session_id, uh_gpsc, uh_ip, uh_browser, uh_referer, uh_url) FROM
> > stdin;
> >
> > so, i excluded this table from my dump and the same error occurs by this
> > command:
> > ALTER TABLE ONLY invoices_lines ADD CONSTRAINT invoices_lines_pkey
> > PRIMARY KEY (nagid, o, linid);
>
> You still haven't given anywhere near enough information to identify the
> bug. I wonder though if any of these tables involve non-built-in
> datatypes? An out-of-date .so file for an add-on datatype could easily
> lead to crashes in these operations.
>
> regards, tom lane

I have composite types in my dump, there are some arrays of them too. There
are no over datatypes.

earlier i had messages by restoring this database like this:

Consider increasing the configuration parameter "checkpoint_segments".
checkpoints are occurring too frequently (17 seconds apart).

So i have increased this parameter and shared memory, but the crash stays.

Best regards, M.Sz.

--
==================================
Michał Szeląg
tel.: +48 693 11 37 55

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message K, Niranjan (NSN - IN/Bangalore) 2008-07-15 13:54:51 Psql or test application hangs when interface is down for the DB server
Previous Message Bruce Momjian 2008-07-15 01:35:41 Re: BUG #4191: Include hint for Windows-like locals in documentation