From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Reiner Dassing <dassing(at)wettzell(dot)ifag(dot)de> |
Cc: | pgsql-admin(at)postgresql(dot)org |
Subject: | Re: Restoring a pg_dump fails with |
Date: | 2001-05-02 14:53:59 |
Message-ID: | 11497.988815239@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Reiner Dassing <dassing(at)wettzell(dot)ifag(dot)de> writes:
> 1. The error "Memory exhausted in AllocSetAlloc(32)" is there on the
> "delete from table" command, also.
I am still unable to reproduce this problem. Are you sure there is not
something you've failed to mention about the table --- rules, triggers,
weird default values, anything?
> 2. There are some warnings during compilation which seems to be strange.
> cc: Info: regproc.c, line 140: In this statement, an array subscript
> expression is either less than zero or greater than the largest value
> that can be represented by the size_t type. (badsubscript)
Your compiler vendors appear not to have read the C specification very
carefully --- array subscripts have integer type not unsigned type,
and there is nothing invalid about the code being complained of.
(The warning in regproc.c is particularly idiotic, because the compiler
should also have been able to deduce that the code being complained of
can never be reached --- it's inside an "if" with a constant condition.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2001-05-02 20:07:51 | Re: Re: Re: disable wal |
Previous Message | Thomas Heller | 2001-05-02 14:25:22 | Re: Re: 7.1 performance |