Re: Unlogged vs. In-Memory
От | Thom Brown |
---|---|
Тема | Re: Unlogged vs. In-Memory |
Дата | |
Msg-id | BANLkTi=_YQec3=AvaFokY8ghcZ3h2oPHxw@mail.gmail.com обсуждение исходный текст |
Ответ на | Unlogged vs. In-Memory (Joshua Berkus <josh@agliodbs.com>) |
Список | pgsql-advocacy |
On 3 May 2011 18:46, Joshua Berkus <josh@agliodbs.com> wrote: > All, > > This has come up a couple times off-list, so I thought we should hammer it out here regarding messaging for 9.1. > > I was discussing the Unlogged Tables feature with an industry analyst. He advised me fairly strongly that we should callit, or at least describe it, as "in-memory tables". While I'm not that sanguine about renaming the feature, I'm happyto use marketing terms in descriptive text in a press release if it gets people interested. > > Our basic issue with the cool features in 9.1 is the elevator pitch problem. Try to describe SSI to a reporter in 20 secondsor less. Unlogged tables suffers from this. "What's an unlogged table? Why is *not* having something a feature?" "long description here ..." "nevermind, I have enough." > > Saying "It's like a in-memory table" is a lot more successful. And it's using the term "in-memory" the same way a lotof other DBMSes market it, i.e. in-memory == non-durable & no disk writes. The important thing from my perspective isthat unlogged tables give us the capabilities of a lot of the "in-memory" databases ... with unlogged tables and fsyncoff, for example, PostgreSQL becomes a viable caching database. > > When doing PR, it's more important to use terms people recognize than to use terms which are perfectly accurate. Nobodyexpects a news article to be perfectly accurate anyway. > > However, I posted this because I think that several folks in the community feel that this is going too far into the landof marketese, and I want to hash it out and get consensus before we start pitching 9.1 final. As far as I'm aware, an unlogged table is just a table which sacrifices crash safety for speed. It's not "in-memory" because that suggests it's always kept in the physical memory, which isn't the case. -- Thom Brown Twitter: @darkixion IRC (freenode): dark_ixion Registered Linux user: #516935 EnterpriseDB UK: http://www.enterprisedb.com The Enterprise PostgreSQL Company
В списке pgsql-advocacy по дате отправления: