=?iso-8859-2?q?Micha=B3_Szel=B1g?= <[EMAIL PROTECTED]> writes:
> Dnia poniedzia³ek, 14 lipca 2008, Tom Lane napisa³:
>> 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 fil
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_ur
=?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 t
Dnia piątek, 11 lipca 2008, Tom Lane napisał:
> "Michal Szelag" <[EMAIL PROTECTED]> writes:
> > i have a server crash by retoring database.
> >
> > I try to retore my database from a custom package with pg_restore and
> > prom a plain package with psql. In both i have the same problem, psl and
> >
"Michal Szelag" <[EMAIL PROTECTED]> writes:
> i have a server crash by retoring database.
> I try to retore my database from a custom package with pg_restore and prom a
> plain package with psql. In both i have the same problem, psl and pg_restore
> outputs:
> pg_restore: [archiver (db)] error ret
The following bug has been logged online:
Bug reference: 4296
Logged by: Michal Szelag
Email address: [EMAIL PROTECTED]
PostgreSQL version: 8.3.3
Operating system: 2.6.23-1-amd64[debian etch]
Description:Server crashes by restoring database
Details:
Hallo,
very sor
