Re: 10 missing features
От | Nicholson, Brad (Toronto, ON, CA) |
---|---|
Тема | Re: 10 missing features |
Дата | |
Msg-id | 2626AEE4839D064CB0472A3814DC403F46D4CA3071@GVW1092EXB.americas.hpqcorp.net обсуждение исходный текст |
Ответ на | Re: 10 missing features (Radosław Smogura <rsmogura@softperience.eu>) |
Список | pgsql-general |
> -----Original Message----- > From: pgsql-general-owner@postgresql.org [mailto:pgsql-general- > owner@postgresql.org] On Behalf Of Radoslaw Smogura > Sent: Tuesday, April 26, 2011 9:55 AM > To: Leif Biberg Kristensen > Cc: pgsql-general@postgresql.org > Subject: Re: [GENERAL] 10 missing features > > > For example, having knowledge when particular query stuck may be great > advantage for administrators and developers as well. Ofcourse each > functionality gives some overhead, but from other hand, if you create > important systems (like financials) "stability" and how it's easy to > track errors is required. For those types of systems - lack of a true audit log is probably a bigger barrier. The biggest "missing feature" are goingto depend on your problem space. > Form this what I was interested and saw: > * I think he good pointed that logging indices, may be unneeded, as > those can be recreated. Whether this is acceptable depends on your system. Yes they can be recreated with a number of caveats -performance for many systems will be poor until some (or all) indexes are back. If you have SLA's based around performanceyou can extend your outage until the indexes get rebuilt. -Indexes are used to enforce primary keys. Are you comfortable running temporarily without your primary keys? -Some replication engines rely on primary keys or unique indexes. Losing these could break replication for you. I think if you could control this on a per-index basis though it could be a win. Brad
В списке pgsql-general по дате отправления: