Re: Restoring a pg_dump fails with

Hello Tom!

Sorry for coming up again with the same problem:
COPY FROM fails with "Memory exhausted in AllocSetAlloc(40)"

After inserting all the data fields by INSERTs I activated  the
following
script by 'psql -e wetter < wetter.sql':

wetter.sql contains the following:

COPY wetter to '/Postgres/backup/h.h';
ALTER TABLE wetter RENAME TO o_wetter;
DROP INDEX wetter_pkey;
DROP INDEX idx_wetter_epoche;
DROP INDEX wetter_wetter_sensor_id_idx;
--
CREATE TABLE "wetter" (
    "sensor_id" int4 NOT NULL REFERENCES sensoren_an_orten,
    "epoche" datetime NOT NULL,
    "wert" float4 NOT NULL,
        PRIMARY KEY (sensor_id,epoche));
REVOKE ALL on "wetter" from PUBLIC;
GRANT ALL on "wetter" to "postgres";
CREATE INDEX wetter_epoche_idx ON wetter(epoche);
CREATE INDEX wetter_sensor_id_idx ON wetter(sensor_id);
--
--
COPY wetter FROM '/Postgres/backup/h.h';
SELECT count(*) FROM o_wetter;
SELECT count(*) FROM wetter;

Now:
The statement "COPY wetter FROM '/Postgres/backup/h.h';"
ends with
"ERROR:  copy: line 1638280, Memory exhausted in AllocSetAlloc(40)"

PostgresLog says:
May  9 09:21:45 sweaty postgres[584514]: [10] DEBUG:  copy: line
1315779, XLogWrite: new log file created - consider increasing WAL_FILES
May  9 09:23:27 sweaty postgres[584514]: [11] ERROR:  copy: line
1638280, Memory exhausted in AllocSetAlloc(40)
May  9 09:23:27 sweaty postgres[584514]: [11] ERROR:  copy: line
1638280, Memory exhausted in AllocSetAlloc(40)
May  9 09:23:27 sweaty postgres[584514]: [12] DEBUG:
AbortCurrentTransaction

This done under Postgres Version 7.1.1
There is no further Trigger, Rule or something.

I hope this helps!

--
Mit freundlichen Gruessen / With best regards
   Reiner Dassing