| From: | "Dave Page" <dpage(at)vale-housing(dot)co(dot)uk> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Андрей Репко <repko(at)sart(dot)must-ipra(dot)com> |
| Cc: | <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Server process exited with unexpected status 128. |
| Date: | 2005-09-26 14:54:28 |
| Message-ID: | E7F85A1B5FF8D44C8A1AF6885BC9A0E4CC2EC7@ratbert.vale-housing.co.uk |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> -----Original Message-----
> From: pgsql-hackers-owner(at)postgresql(dot)org
> [mailto:pgsql-hackers-owner(at)postgresql(dot)org] On Behalf Of Tom Lane
> Sent: 26 September 2005 15:47
> To: Андрей Репко
> Cc: pgsql-hackers(at)postgresql(dot)org
> Subject: Re: [HACKERS] Server process exited with unexpected
> status 128.
>
> [ looking again... ]
>
> =?Windows-1251?Q?=C0=ED=E4=F0=E5=E9_=D0=E5=EF=EA=EE?=
> <repko(at)sart(dot)must-ipra(dot)com> writes:
> > max_stack_depth = 65536 # min 100, size in KB
>
> Hmm, maybe this is the problem. Are we sure Windows will
> allow a 64M stack?
Looks like we used 4MB in the backend by default:
http://archives.postgresql.org/pgsql-committers/2005-01/msg00386.php
Regards, Dave.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-26 15:01:17 | Re: Server process exited with unexpected status 128. |
| Previous Message | Tom Lane | 2005-09-26 14:47:20 | Re: Server process exited with unexpected status 128. |