A basic issue to answer (reminiscent of the past!) is whether or notto support PG 7.0, or bite the bullet and support PG 7.1 only for ACS4.0. PG 7.1 goes beta in a couple of weeks...I raise this because 7.1 includes a new function manager thatcorrectly handles NULLs, which would really help us out a lot (havingstruggled with this in the past).Name length is a compile-time configurable number, though we probablywant to stick with the default 32 characters.Max size of varchar is roughly the same as blocksize, which werecommend be set to 16KB. We've been using a compressed text type(which I believe Interbase does, too) so in practice you getconsiderably longer varchars. 7.1 will include a transparentlarge-object feature that will allow varchars of any length, andlargely remove the row length restrictions which have plagued PG inthe past (at some expense in performance, but certainly no worse andprobably better than the explicit CLOBs used in Oracle).Indices are limited to a bit over 2KB, which shouldn't be a problemunless aD now indexes keys over the old 700 or so byte limit Oracleallows with a default block size.
