simultaneous checking

[Alan DeKok]

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?

> radheck/radgroupcheck are obviously a different matter, and capping the
> length of those fields (which after all go into AVPs) makes sense. I
> would still recommend varchar(253) rather than some arbitrary shorter
> length though.

  Sure.

  Alan DeKok.