The CANDIS Blog

In the middle of putting out a proposal for a very large client/tender at the moment. Well over a life time’s earnings in servers and an as yet un calculated retainer and service rate at this stage – electricity and bandwidth and human hours all cost money.

I always try to get the best prices within the scope of common sense for clients. Mainly because as a integrated stack vendor, the pricing on one component can blow out the total price of the whole stack. And hardware is the first place to start (given an understanding of the management systems and risk credentials of the project at hand already).

One thorn in my side is mandated “Installation and Configuration” charges. Which are basically extortion attempts.

(more…)

Ever had a situation like this:

Select from database ID where name = RICHARD;

Returns and ID of 55 for example.

Then go and do a query like this:

Select * from some_other_table where ID = 55;

Returns, “Sorry does not exist, time to die…..”

Well apparently indexes when corrupt – which is NOT SUPPOSED TO HAPPEN – can cause PostgreSQL to go all stupid and not do a table lookup for real. This happened to me. So I found this:

PlanetPostgresql

Turns out that a reindex and a full vacuum can do wonders – even though a full vacuum is not needed with autovacuum and indexes can’t get corrupted…..or so they say.

I have now added a system wide reindex maintenance plan for PostgreSQL every night. I know that MS-SQL server has an option for this with their maintenance jobs inside enterprise manager. Maybe someone should make an enterprise manager for PostgreSQL too?