From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Claudio Freire <klaussfreire(at)gmail(dot)com>, knizhnik <knizhnik(at)garret(dot)ru>, Amit Kapila <amit(dot)kapila16(at)gmail(dot)com>, James Mansion <james(at)mansionfamily(dot)plus(dot)com>, David Fetter <david(at)fetter(dot)org>, PG Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
Date: | 2014-01-10 19:02:06 |
Message-ID: | 14942.1389380526@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-announce pgsql-hackers |
Robert Haas <robertmhaas(at)gmail(dot)com> writes:
> I've often thought that 64-bit machines are so capable that there's no
> reason to go any higher. But lately I've started to wonder. There
> are already machines out there with >2^40 bytes of physical memory,
> and the number just keeps creeping up. When you reserve a couple of
> bits to indicate user or kernel space, and then consider that virtual
> address space can be many times larger than physical memory, it starts
> not to seem like that much.
> But I'm not that excited about the amount of additional memory we'll
> eat when somebody decides to make a pointer 16 bytes. Ugh.
Once you really need that, you're not going to care about doubling
the size of pointers. At worst, you're giving up 1 bit of address
space to gain 64 more.
(Still, I rather doubt it'll happen in my lifetime.)
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | David Fetter | 2014-01-13 04:25:39 | == PostgreSQL Weekly News - January 12 2014 == |
Previous Message | Robert Haas | 2014-01-10 18:51:05 | Re: [ANNOUNCE] IMCS: In Memory Columnar Store for PostgreSQL |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2014-01-10 19:07:12 | Re: [PATCH] Negative Transition Aggregate Functions (WIP) |
Previous Message | Alvaro Herrera | 2014-01-10 19:02:01 | Re: new json funcs |