agora inbox for postgres@postgres.berkeley.edu
help / color / mirror / Atom feedproblems with memory
2+ messages / 2 participants
[nested] [flat]
* problems with memory
@ 1995-02-05 15:54 David Bigagli <david@naxos.caspur.it>
0 siblings, 1 reply; 2+ messages in thread
From: David Bigagli @ 1995-02-05 15:54 UTC (permalink / raw)
To: legacy; +Cc: david@naxos.caspur.it
Hi,
we install Postgres on alpha axp 3000/500 running osf/1 v2.1.
Installation was ok. We found problems using copy command with a ascii file
which dimension is 89373089 bytes. After two houres the copy aborts
with the message "FATAL 1:Feb 4 22:54:39:palloc failure: memory exhausted".
Then we use the command vacuum on the same database and also after two
houres vacuum abborts with the same error message.
Do you have any idea about?? May be is shared memory problem??
Does it is normal that these commands take this long time to run?
Thanks,
Regards,....David
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/
^ permalink raw reply [nested|flat] 2+ messages in thread
* Re: problems with memory
@ 1995-02-07 05:26 Paul M. Aoki <aoki@cs.berkeley.edu>
parent: David Bigagli <david@naxos.caspur.it>
0 siblings, 0 replies; 2+ messages in thread
From: Paul M. Aoki @ 1995-02-07 05:26 UTC (permalink / raw)
To: David Bigagli <david@naxos.caspur.it>; +Cc: legacy
David Bigagli <david@naxos.caspur.it> writes:
> Installation was ok. We found problems using copy command with a ascii file
> which dimension is 89373089 bytes. After two houres the copy aborts
> with the message "FATAL 1:Feb 4 22:54:39:palloc failure: memory exhausted".
you're likely hitting process virtual memory limits (based on
available swap space). each copy command runs in one transaction and
some types of memory are only freed between transactions.
i would try splitting the file into smaller chunks and loading them
with separate copy commands.
--
Paul M. Aoki | University of California at Berkeley
aoki@CS.Berkeley.EDU | Dept. of EECS, Computer Science Division (#1776)
| Berkeley, CA 94720-1776
==============================================================================
To add/remove yourself to/from the POSTGRES mailing list: send mail with
the subject line ADD or DEL to "postgres-request@postgres.Berkeley.EDU".
If this fails, send mail to "post_questions@postgres.Berkeley.EDU" and
a human will deal with it. DO NOT post to the "postgres" mailing list.
==============================================================================
URL: http://s2k-ftp.CS.Berkeley.EDU:8000/postgres/
^ permalink raw reply [nested|flat] 2+ messages in thread
end of thread, other threads:[~1995-02-07 05:26 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
1995-02-05 15:54 problems with memory David Bigagli <david@naxos.caspur.it>
1995-02-07 05:26 ` Paul M. Aoki <aoki@cs.berkeley.edu>
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox