| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Subject: | Re: PostgreSQL as a local in-memory cache |
| Date: | 2010-06-18 20:56:42 |
| Message-ID: | 4C1BDD8A.3060704@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
On 6/18/10 2:15 AM, Matthew Wakeling wrote:
> I'd like to point out the costs involved in having a whole separate
> "version" of Postgres that has all this safety switched off. Package
> managers will not thank anyone for having to distribute another version
> of the system, and woe betide the user who installs the wrong version
> because "it runs faster". No, this is much better as a configurable option.
Agreed, although initial alphas of this concept are likely to in fact be
a separate source code tree. Eventually when we have it working well it
could become an initdb-time option.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Scott Carey | 2010-06-19 02:59:14 | Re: requested shared memory size overflows size_t |
| Previous Message | Josh Berkus | 2010-06-18 20:55:28 | Re: PostgreSQL as a local in-memory cache |