| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Chris Ruprecht <chrup999(at)yahoo(dot)com> |
| Cc: | PostGreSQL Admin Group <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Problems with upgrading 7.1.3 -> 7.2 |
| Date: | 2002-02-09 18:06:46 |
| Message-ID: | 11435.1013278006@sss.pgh.pa.us |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Chris Ruprecht <chrup999(at)yahoo(dot)com> writes:
> I then went ahead to create the indexes and this is where the fun begins:
> psql:/tmp/phones.schema.2:136: ERROR: tuplesort: unexpected end of data
Is it possible you were running out of disk space here? I would not
have expected that particular error message as a result, but it seems
like a plausible theory otherwise.
There really is not enough detail in your report to allow any other
constructive comments. You haven't told us what went wrong with
pg_restore, nor exactly what the "file is too large" error message
was (nor what command caused it), nor the commands that produced any
of the errors other than the one above. A backtrace from the apparent
backend coredump at line 168 would be useful too.
I would like to dig into this to find and fix the underlying problems,
but there's not a darn thing I can do given this amount of detail.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Simone Tellini | 2002-02-09 21:56:16 | pg_dump / pg_upgrade problem |
| Previous Message | Chris Ruprecht | 2002-02-09 17:36:52 | Problems with upgrading 7.1.3 -> 7.2 |