Re: Problems Importing table to pgadmin

From: Adrian Klaver <adrian(dot)klaver(at)aklaver(dot)com>
To: metaresolve <solvemetare(at)gmail(dot)com>, pgsql-general(at)postgresql(dot)org
Subject: Re: Problems Importing table to pgadmin
Date: 2016-12-08 01:25:52
Message-ID: 618177f3-14f7-5ae3-513d-4854e7936d90@aklaver.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On 12/07/2016 05:19 PM, metaresolve wrote:
> Uh, yeah, it was a SELECT * from cc_20161207;
>
> I know, it was dumb. I didn't realize it would break it or at least run for
> a while. I tend to do things in small steps, run a query, check my results,
> then tweak.
>
> You're right, I wouldn't want to be viewing those million. so I guess I
> could just be doing the top 10000 rows to get a sense, then be doing my
> aggregate group bys/etc to get my final numbers? That's how I hacked Access
> to be my data analysis program until I got to Alteryx. But I was also never
> using files of 1M then.
>

FYI pgAdmin, if I remember correctly, has a setting that limits the
maximum number of rows that it will fetch at a time.

--
Adrian Klaver
adrian(dot)klaver(at)aklaver(dot)com

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Sreekanth Palluru 2016-12-08 01:55:39 Fwd: ERROR invalid page header in block xxx of relation base/xxxxx/xxxxx/
Previous Message metaresolve 2016-12-08 01:19:30 Re: Problems Importing table to pgadmin