Re: Large Tables(>1 Gb)

On Thu, 29 Jun 2000 Fred_Zellinger(at)seagate(dot)com wrote:

> I look around at some backend configuration parameters to see if I can get
> Postgres to do some neat memory stuff(but later realize that it was the
> front-end and not the backend that was eating up memory...I tried pg_dump
> on the database/table, and stuff started spooling right away)

> Rather than trying to fix the problem, I decided to subvert it by breaking
> my table into a bunch of little tables, each one less than my RAM size, so
> that I would never dig into SWAP space on a select *....(all of you who are
> laugh at me, you can just quit reading right now).

*stops laughing* ;-)

> Anyway, just wanted to see if all my assumptions are correct, or if anyone
> has a better explanation for my observation, and/or some solutions.

If you want to SELECT 1GB of data into RAM, you ought to have over 1GB of
RAM, don't you think?

What exactly is the problem you're trying to fix?

- Andrew