Dnia poniedziałek, 14 lipca 2008, Tom Lane napisał: > =?iso-8859-2?q?Micha=B3_Szel=B1g?= <[EMAIL PROTECTED]> 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 -- Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-bugs
