Re: Asynchronous commit | Transaction loss at server crash

Поиск
Список
Период
Сортировка
От Balkrishna Sharma
Тема Re: Asynchronous commit | Transaction loss at server crash
Дата
Msg-id BAY149-w47C0EFBE3720C0DA258E4AF0E30@phx.gbl
обсуждение исходный текст
Ответ на Re: Asynchronous commit | Transaction loss at server crash  (Scott Marlowe <scott.marlowe@gmail.com>)
Ответы Re: Asynchronous commit | Transaction loss at server crash  (Scott Marlowe <scott.marlowe@gmail.com>)
Список pgsql-admin
What if we don't rely on the cache of SSD, i.e. have write-through setting and not write-back. Is the performance gain then not significant to justify SSD ?

> Date: Thu, 20 May 2010 13:35:54 -0600
> Subject: Re: [ADMIN] Asynchronous commit | Transaction loss at server crash
> From: scott.marlowe@gmail.com
> To: b_ki@hotmail.com
> CC: pgsql-admin@postgresql.org
>
> SSD and battery backed cache kind of do the same thing, in that they
> reduce random access times close to 0. However, most SSDs are still
> not considered reliable due to their internal caching systems. hard
> drives and bbu RAID are proven solutions, SSD is still not really
> there just yet in terms of being proven reliable.
>
> On Thu, May 20, 2010 at 1:02 PM, Balkrishna Sharma <b_ki@hotmail.com> wrote:
> > Good suggestion. Thanks.
> > What's your take on SSD ? I read somewhere that moving the WAL to SSD helps
> > as well.
> >
> >> Date: Thu, 20 May 2010 11:36:31 -0600
> >> Subject: Re: [ADMIN] Asynchronous commit | Transaction loss at server
> >> crash
> >> From: scott.marlowe@gmail.com
> >> To: b_ki@hotmail.com
> >> CC: pgsql-admin@postgresql.org
> >>
> >> On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma <b_ki@hotmail.com>
> >> wrote:
> >> > I need to support several hundreds of concurrent update/inserts from an
> >> > online form with pretty low latency (maybe couple of milliseconds at
> >> > max).
> >> > Think of a save to database at every 'tab-out' in an online form.
> >>
> >> You can get nearly the same performance by using a RAID controller
> >> with battery backed cache without the same danger of losing
> >> transactions.
> >>
> >> --
> >> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> >> To make changes to your subscription:
> >> http://www.postgresql.org/mailpref/pgsql-admin
> >
> > ________________________________
> > The New Busy is not the too busy. Combine all your e-mail accounts with
> > Hotmail. Get busy.
>
>
>
> --
> When fascism comes to America, it will be intolerance sold as diversity.
>
> --
> Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
> To make changes to your subscription:
> http://www.postgresql.org/mailpref/pgsql-admin


The New Busy is not the old busy. Search, chat and e-mail from your inbox. Get started.

В списке pgsql-admin по дате отправления:

Предыдущее
От: Scott Marlowe
Дата:
Сообщение: Re: Asynchronous commit | Transaction loss at server crash
Следующее
От: Scott Marlowe
Дата:
Сообщение: Re: Asynchronous commit | Transaction loss at server crash