Re: PostgreSQL survey

On Dec 9, 2011, at 3:42 PM, Cesar Massaki Kamiya wrote:<br /><blockquote type="cite">1. Anyone using PostgreSQL for
enterprisemission critical system ?<br /></blockquote><br />Enova Financial runs all of our OLTP and a large portion of
ourreporting on Postgres. Our largest OLTP database is ~1.8TB and the last time I measured it (almost 2 years ago) it
averaged640TPS and peaked at over 4kTPS.<br /><br />Downtime on that database costs the company well over
$100k/hour.<br/><br /><blockquote type="cite">2. How big are the servers you are running PostgreSQL, Is there anyone
usingmore than 32 cores or 256GB memory ?<br /></blockquote><br />We don't currently have anything over 32 cores, but
wehave several servers with 1/2TB of memory. The vast majority of that memory is used by the filesystem cache.<br /><br
/><blockquotetype="cite">3. What OS you are using to run this mission critical system on PostgreSQL ? Linux, Unix ?<br
/></blockquote><br/>Linux.<br /><br /><blockquote type="cite">4. Who provides PostgreSQL support ?  Do you have any
supportcontract with a third party company ? If so, how much is the monthly support fee ?<br /></blockquote><br />We
useCommand Prompt for our formal support contract, but we have also used consulting services from PgX and 2nd
Quadrant.<br/><br />As others have mentioned, support on the mailing list is generally excellent and you will have a
challengehiring someone that is highly knowledgable in Postgres (I would estimate the pool of people who could be
consideredexperts in Postgres and would consider a job offer in the US to be less than 1000). Your best bet may be to
findsomeone who is experienced in a number of other RDBMSes and is willing to learn Postgres. Just make sure to bump up
theircompensation as they become experienced or you risk loosing them (my rule of thumb is that PG knowledge is worth
~25%more than comparable Oracle knowlege).<br />--<br />Jim C. Nasby, Database Architect                  
jim@nasby.net<br/>512.569.9461 (cell)                         http://jim.nasby.net<br /><br /><br />