From: | Stefan Holzheu <stefan(dot)holzheu(at)bitoek(dot)uni-bayreuth(dot)de> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | ADMIN <pgsql-admin(at)postgresql(dot)org> |
Subject: | Re: Problems with pg_dump |
Date: | 2004-01-26 15:31:12 |
Message-ID: | 401532C0.5010402@bitoek.uni-bayreuth.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
>
>>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?
Tabelle »messungen.aggr_stddev_hour«
Spalte | Typ | Attribute
--------+--------------------------+-----------
id | integer | not null
von | timestamp with time zone | not null
wert | double precision |
counts | integer | not null
Indexe:
»idx_aggr_stddev_hour_id_von« eindeutig, btree (id, von)
Encoding: LATIN9
The error does not occur always and not always with the same table.
However, the error occurs only on that kind of aggregation tables. There
is a cron-job keeping the tables up to date, starting all 10 minutes.
The job does delete and inserts on the table. Could this somehow block
the dump process? Normally it should not?
>
>
>>The database size is about 10 GB.
>
>
> How big is the particular table?
The table has 9 000 000 entries.
Stefan
--
-----------------------------
Dr. Stefan Holzheu
Tel.: 0921/55-5720
Fax.: 0921/55-5799
BITOeK Wiss. Sekretariat
Universitaet Bayreuth
D-95440 Bayreuth
-----------------------------
From | Date | Subject | |
---|---|---|---|
Next Message | Robert Treat | 2004-01-26 16:05:45 | Re: Can't connect to phppgadmin |
Previous Message | Tom Lane | 2004-01-26 14:39:58 | Re: Problems with pg_dump |