| From: | John R Pierce <pierce(at)hogranch(dot)com> |
|---|---|
| To: | pgsql-general(at)postgresql(dot)org |
| Subject: | Re: Problems Importing table to pgadmin |
| Date: | 2016-12-08 01:07:40 |
| Message-ID: | a0ba71db-30f6-4a43-41c8-36fe4bf45712@hogranch.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
On 12/7/2016 4:02 PM, metaresolve wrote:
> I used to use Access to do my data crunching, matching, and cleaning at my
> old job. I worked with a max of 600k records so Access could handle it. I
> know, lame, but it's what I knew.
Access is really 2 completely different things bundled. One is that
rather weak and poor "Jet" sorta-relational database that sorta
implements a subset of SQL. The other is a database application
development system oriented around forms and reports.
> My thought was to use postgreSQL as a kind of more advanced Access that I
> could use to crunch numbers on similarly. However, My file has 1.1M records
> on it and pgadmin seems to be choking on it.
Postgres, on a properly scaled and tuned database server, can handle
billions of records. Obviously, doing something silly like querying
all billions at once will never be fast, thats a lot of data to marshal
and process.
--
john r pierce, recycling bits in santa cruz
| From | Date | Subject | |
|---|---|---|---|
| Next Message | metaresolve | 2016-12-08 01:19:30 | Re: Problems Importing table to pgadmin |
| Previous Message | Adrian Klaver | 2016-12-08 01:05:48 | Re: Problems Importing table to pgadmin |