markw wrote:
>
> Hiroshi Inoue wrote:
>
> >markw wrote:
[snip]
> >>Actually, I tracked it down. It may be something that you are
> >>interested in, I had my stack set to 64K, when I bumped it up to 256K,
> >>the problem went away.
> >>
> >>Both the unixODBC and PostgreSQL drivers are similar, or at least have
> >>a similar origin. The stack utilization deserve at least a little
> >>scrutiny.
> >>
> >>
> >
> >I've improved a little about the stack utilization of
> >our ODBC driver and some applications could work with
> >the improvement though I'm not sure if it can work with
> >your application.
> >
> >
> well, I'm flexable, and I'm sure it would be helpful to many other
> developers, what is a good estimate for thread stack size?
Though the unixODBC and PostgreSQL drivers have a similar origin,
they are pretty different now. As for stack utilization, I removed
MAX_MESSAGE_LEN(65536) byte buffers completely and so most
applications may be able to work with 64K stack size.
regards,
Hiroshi Inoue
http://w2422.nsk.ne.jp/~inoue/
