| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Michał Szeląg <msz(at)szel(dot)pl> |
| Cc: | pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4296: Server crashes by restoring database |
| Date: | 2008-07-14 14:30:28 |
| Message-ID: | 7979.1216045828@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
=?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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Yishai Lerner | 2008-07-14 21:04:41 | BUG #4306: TSearch2 stemming, stop words and lexize behaviour inconsistent |
| Previous Message | Michał Szeląg | 2008-07-14 07:38:38 | Re: BUG #4296: Server crashes by restoring database |