From: | Hiroshi Inoue <Inoue(at)tpf(dot)co(dot)jp> |
---|---|
To: | markw <markw(at)mohawksoft(dot)com> |
Cc: | pgsql-odbc(at)postgresql(dot)org |
Subject: | Re: Threading crash using ODBC |
Date: | 2002-11-18 03:55:53 |
Message-ID: | 3DD864C9.D0865217@tpf.co.jp |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-odbc |
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/
From | Date | Subject | |
---|---|---|---|
Next Message | Han | 2002-11-18 07:41:05 | what's the latest protocol version? |
Previous Message | Hiroshi Inoue | 2002-11-18 03:18:38 | Re: FATAL 1: Sorry, too many clients already |