商业postgresql [英] Commercial postgresql
问题描述
嗨..
在讨论了如何处理PG中的错误以及MySQL和Postgresql中的开发
文化之后，我的老板对此表示赞同它可能比MySQL 4.x（InnoDB）更好，但是......
他喜欢了解其他使用Postgres和简单复制的人（我们
需要24/7系统），了解postgres的表现，以及
如何稳定它的数据和备份功能等。 />
是否有一些详细的商业案例，他/我们可以阅读感觉
更确定PG是一个不错的选择？
/ BL
---------------------------（播出结束）---- -----------------------
提示3：如果通过Usenet发布/阅读，请发送适当的
subscribe-nomail命令 ma*******@postgresql.org 以便您的
消息可以干净利落地到达邮件列表
Hi ..
Well after discussing how bugs are handled in PG, and the development
culture in both MySQL and Postgresql, my boss agress that it may be a
good aletenertive til MySQL 4.x (InnoDB), but ...
He likes to know about others using Postgres and simple replication (we
need it in at 24/7 system), to know how postgres performs, and how
stable it is regarding its data and the backup feature etc.
Are there some detailed busisness cases, that he/we can read to feel
more assured that PG is a good choice ?
/BL
---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to ma*******@postgresql.org so that your
message can get through to the mailing list cleanly
推荐答案
2003年8月30日星期六16:18:14 +0200（CEST）， pe ***** @ gmx.net （Peter
Eisentraut）写道：
On Sat, 30 Aug 2003 16:18:14 +0200 (CEST), pe*****@gmx.net (Peter
Eisentraut) wrote:
很多，但通常很难得到客户同意这种事情。
many, but it''s usually difficult to get customers to agree to this sort of
thing.
为什么会这样？
Why is that?
哎呀！ Jacob Hanson< ja ********* @ firsthealth.com>看到喷涂在墙上：
Oops! Jacob Hanson <ja*********@firsthealth.com> was seen spray-painting on a wall:
2003年8月30日星期六16:18:14 +0200（CEST）， pe ***** @ gmx.net （Peter
Eisentraut）写道：
On Sat, 30 Aug 2003 16:18:14 +0200 (CEST), pe*****@gmx.net (Peter
Eisentraut) wrote:
很多，但通常很难让客户同意这种事情。
many, but it''s usually difficult to get customers to agree to this sort of
thing.
为什么会这样？
Why is that?
因为：
1.他们使用的工具可能是他们认为具有竞争优势的b $ b优势。
2.如果继续使用像这样的一个列表，它们成为了_b $ _
甲骨文销售人员等的明显目标。
这些原因可能偶尔会被克服，但这并不是他们
无关紧要。
-
选择''cbbrowne''|| '''''|| ''cbbrowne.com';
http://cbbrowne.com/ info / linux.html
流行度是平庸的标志。 --Niles Crane，Frasier
Because:
1. What tools they use may be something they consider a "competitive
advantage."
2. If they go on a list like this, they become _obvious_ targets for
Oracle sales people and such.
Those reasons may occasionally be overcome, but that doesn''t make them
irrelevant.
--
select ''cbbrowne'' || ''@'' || ''cbbrowne.com'';
http://cbbrowne.com/info/linux.html
"Popularity is the hallmark of mediocrity." --Niles Crane, "Frasier"
>>>>> " BL" == Bo Lorentsen< bl@netgroup.dk>写道：
BL>嗨..
BL>他喜欢了解使用Postgres和简单复制的其他人（我们
BL>需要在24/7系统中使用它），知道postgres的表现如何，以及
BL> ;稳定它是关于它的数据和备份功能等。
我在24/7/365系统中使用它，该系统大量写入和读取
来自。我的缺点是：
1）升级到主要版本需要转储/恢复，这对于大型数据库来说是一个很大的停机时间。
2）需要在桌子上运行真空以防止它们膨胀。
多。在我的系统非常繁忙，有时运行真空
推动磁盘超出其极限并使整个系统减速到
爬行。
3）索引膨胀显然是一个比我想象的更大的问题。
昨天我重新索引了所有表格。在一个2.7Gb
的数据库中（那些注意到我的数字不断变化的人...这个
是正确的值 - 我之前读错了）我只是刮了900Mb
''死''索引页面。不幸的是，我最大的92M行表
需要大约43分钟*每个索引*才能重新索引。
我认为2可能会被放大3.我们'在索引优化后，本周将看看系统如何保持
。
BL>是否有一些详细的商业案例，他/我们可以阅读感觉
BL>更确定PG是一个不错的选择？
如果你想获得商业支持，它就在那里。至少有两家公司提供它。
-
= - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - = - =
Vivek Khera，博士。 Khera Communications，Inc。
互联网： kh***@kciLink.com Rockville，MD + 1- 240-453-8497
AIM：vivekkhera Y！：vivek_khera http://www.khera.org/~vivek/
--------------------- ------（广播结束）---------------------------
提示5：有您查看了我们广泛的常见问题解答？
http： //www.postgresql.org/docs/faqs/FAQ.html
>>>>> "BL" == Bo Lorentsen <bl@netgroup.dk> writes:
BL> Hi ..
BL> He likes to know about others using Postgres and simple replication (we
BL> need it in at 24/7 system), to know how postgres performs, and how
BL> stable it is regarding its data and the backup feature etc.
I use it in 24/7/365 system which is heavily written to and read
from. The drawbacks I have are:
1) upgrade to major versions require dump/restore which is a
significant amount of downtime for a large DB.
2) the need to run vacuum on tables to keep them from bloating too
much. on my system which is very busy, sometimes running vacuum
pushes the disk beyond its limits and slows the whole system to a
crawl.
3) Index bloat is apparently a bigger problem than I thought.
Yesterday I took the hit of reindexing all my tables. On a 2.7Gb
database (those of you who notice my numbers keep changing... this
is the correct value -- I read wrongly before) I just shaved 900Mb
of ''dead'' index pages. Unfortunately, my largest table of 92M rows
takes about 43 minutes *per index* to reindex.
I think 2 is probably amplified by 3. We''ll see how the system holds
up this week after the indexes have been optimized.
BL> Are there some detailed busisness cases, that he/we can read to feel
BL> more assured that PG is a good choice ?
If you want commercial support, it is out there. There are at least
two companies offering it.
--
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Vivek Khera, Ph.D. Khera Communications, Inc.
Internet: kh***@kciLink.com Rockville, MD +1-240-453-8497
AIM: vivekkhera Y!: vivek_khera http://www.khera.org/~vivek/
---------------------------(end of broadcast)---------------------------
TIP 5: Have you checked our extensive FAQ?
http://www.postgresql.org/docs/faqs/FAQ.html
这篇关于商业postgresql的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！
