| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Stefan Holzheu <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)de> |
| Cc: | ADMIN <pgsql-admin(at)postgresql(dot)org> |
| Subject: | Re: Problems with pg_dump |
| Date: | 2004-01-26 14:39:58 |
| Message-ID: | 7276.1075127998@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-admin |
Stefan Holzheu <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)de> writes:
> Two weeks ago we did an upgrade from postgresql 7.3.2 to 7.4.1.
> No we have the problem that pg_dump does not finish. We get the
> following error message:
> pg_dump: lost synchronization with server: got message type "5", length
> 842281016
> pg_dump: SQL command to dump the contents of table "aggr_stddev_hour"
> failed:
That's interesting. What are the column data types in that table? What
character set encoding are you using? Can you do a dump if you select
the dump-data-as-INSERT-commands option?
> The database size is about 10 GB.
How big is the particular table?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stefan Holzheu | 2004-01-26 15:31:12 | Re: Problems with pg_dump |
| Previous Message | Robert Treat | 2004-01-26 14:30:35 | Re: Selects query inside function must read commited data |