That's the only error I got. It spit out a few rows showing SQL
commands being processed, then it would die with "out of memory" or
just return to the command prompt.
I ended up destroying the DB and re-creating it since it didn't have
any critical data in it.
-A
On Wed, Oct 14, 2015 at 12:31 AM, Greg Stark <stark@mit.edu> wrote:
> On Fri, Sep 25, 2015 at 3:06 AM, <aaron@heyaaron.com> wrote:
>> It runs for a few minutes, and then I either get an out of memory error, or
>> it appears to exit normally without importing the data.
>>
>> Thinking it was because my 'dev' server is only 512 MB, I temporarily scaled
>> it up to 8 GB. Same error.
>
> I would suggest posting the actual error. There are various errors
> that can be read as "out of memory" but they're not really the same
> thing. If you had free memory on the machine then which error it was
> specifically might be important. Also Postgres prints more information
> than just "out of memory" and that additional context could be
> helpful.
>
> --
> greg
