22 Jul
2009
22 Jul
'09
4:04 a.m.
On Wed, Jul 22, 2009 at 02:23:30AM +0100, Alan DeKok wrote:
Phil Mayers wrote:
After the 2nd outage this caused (we rely on near realtime accounting) I looked into it, and found that postgresql suffers no performance benefit from using "varchar(n)" and I simply altered all the "varchar" fields to type "text". We have since experienced no such problems. So, at the very least I'd recommend changing the default postgresql accounting schema.
Patch?
I must admit, I'd assumed someone had a specific reason for the field sizes being what they are, and didn't want to pre-empt them. But if there isn't such a reason, I'll knock one up.