http://pabivano.t35.com/
_
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-U
Excerpts from Mikko Partio's message of jue may 20 00:39:00 -0400 2010:
> On Wed, May 19, 2010 at 3:21 PM, Ray Stell wrote:
> > http://archives.postgresql.org/pgsql-general/2007-06/msg01050.php
>
> Browsing through that thread I can see that I have similar symptoms:
>
> $ pg_controldata | grep
Hello,Couple of questions:1. For the 'Asynchronous commit' mode, I know that
WAL transactions not flushed to permanent storage will be lost in event of a
server crash. Is it possible to know what were the non-flushed transactions
that were lost, in any shape/form/part ? I guess not, but wanted
Excerpts from Narasimha Murthy-VRFX87's message of jue may 20 02:47:21 -0400
2010:
> Hi Alvaro Herrera,
>
> Since, my original plan was to run the auto-vacuum daily EXACTLY at 5 am, I
> wanted to know which seconds of a minute. My query in other word was, if I
> set autovacuum_naptime to 1 hr,
On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma wrote:
> Hello,
> Couple of questions:
> 1. For the 'Asynchronous commit' mode, I know that WAL transactions not
> flushed to permanent storage will be lost in event of a server crash. Is it
That's not exactly correct. Transactions that haven'
On Thu, May 20, 2010 at 10:54 AM, Balkrishna Sharma 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
All,
I downloaded the file for Sun solaris 8.4 version, and extracted. Can
someone tell me where the configure script is? Which unix account should
run this script? You help is very appreciated.
15.5. Installation Procedure
1. Configuration
The first step of the installation procedur
On Thu, May 20, 2010 at 11:56 AM, wrote:
>
> All,
>
> I downloaded the file for Sun solaris 8.4 version, and extracted. Can
> someone tell me where the configure script is? Which unix account should
> run this script? You help is very appreciated.
It looks like you're compiling from source
And don't include
pgsql-admin-ow...@postgresql.org
in your cc list etc... Just pgsql-admin is plenty.
--
Sent via pgsql-admin mailing list (pgsql-admin@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-admin
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.marl...@gmail.com
> To: b...@hotmail.com
> CC: pgsql-ad
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
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.marl...
The design of SSD is such that it cannot run without caching. It has
to cache to arrange things to be written out due to issues with the
fact that it cannot write small blocks one at a time but needs to
write large chunks together at once.
On Thu, May 20, 2010 at 2:10 PM, Balkrishna Sharma wrote
But if we have write-through setting, failure before the cache can write to
disk will result in incomplete transaction (i.e. host will know that the
transaction was incomplete). Right ?
Two things I need for my system is:1. Unsuccessful transactions with a
notification back that it is unsuccess
On Thu, May 20, 2010 at 2:26 PM, Balkrishna Sharma wrote:
> But if we have write-through setting, failure before the cache can write to
> disk will result in incomplete transaction (i.e. host will know that the
> transaction was incomplete). Right ?
> Two things I need for my system is:
> 1. Unsuc
On 2010-05-20 22:26, Balkrishna Sharma wrote:
But if we have write-through setting, failure before the cache can write to
disk will result in incomplete transaction (i.e. host will know that the
transaction was incomplete). Right
Two things I need for my system is:1. Unsuccessful transactio
Jesper Krogh wrote:
A Battery Backed raid controller is not that expensive. (in the range
of 1 or 2 SSD disks).
And it is (more or less) a silverbullet to the task you describe.
Maybe even less; in order to get a SSD that's reliable at all in terms
of good crash recovery, you have buy a fairl
On Thu, May 20, 2010 at 4:04 PM, Greg Smith wrote:
> Also, it's questionable whether a SSD is even going to be faster than
> standard disks for the sequential WAL writes anyway, once a non-volatile
> write cache is available. Sequential writes to SSD are the area where the
> gap in performance b
Balkrishna Sharma 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.
I regularly see 2000 - 4000 small write transactions per
http://tikiboma.tripod.com/
_
Hotmail is redefining busy with tools for the New Busy. Get more from your
inbox.
http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:e
On 2010-05-21 00:04, Greg Smith wrote:
Jesper Krogh wrote:
> A Battery Backed raid controller is not that expensive. (in the
> range of 1 or 2 SSD disks). And it is (more or less) a silverbullet
> to the task you describe.
Maybe even less; in order to get a SSD that's reliable at all in
terms
On Thu, May 20, 2010 at 7:53 PM, Alvaro Herrera wrote:
> Excerpts from Mikko Partio's message of jue may 20 00:39:00 -0400 2010:
> > On Wed, May 19, 2010 at 3:21 PM, Ray Stell wrote:
>
> > > http://archives.postgresql.org/pgsql-general/2007-06/msg01050.php
> >
> > Browsing through that thread I c
22 matches
Mail list logo
