Re: BUG #4296: Server crashes by restoring database - Mailing list pgsql-bugs

From Tom Lane
Subject Re: BUG #4296: Server crashes by restoring database
Date
Msg-id 7979.1216045828@sss.pgh.pa.us
Whole thread Raw
In response to Re: BUG #4296: Server crashes by restoring database  (Michał Szeląg <msz@szel.pl>)
Responses Re: BUG #4296: Server crashes by restoring database  (Michał Szeląg <msz@szel.pl>)
List pgsql-bugs
Michał Szeląg <msz@szel.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


pgsql-bugs by date:

Previous
From: Michał Szeląg
Date:
Subject: Re: BUG #4296: Server crashes by restoring database
Next
From: Bruce Momjian
Date:
Subject: Re: BUG #4191: Include hint for Windows-like locals in documentation