> #0 0xc00a9098 in memset ()
> (gdb) backtrace
> #0 0xc00a9098 in memset ()
> #1 0x15d0e8 in PostgresMain (argc=-534762622, argv=0x203cb000,
> real_argc=-534763790, real_argv=0x203cb000) at postgres.c:1582
> #2 0xe0202530 in ?? ()
> Cannot access memory at address 0x203cafe8.
>
> (gdb) fra
Hi,
> So any multiple occurence of parse errors crashes your
> backend. Can you get coredump from the crashing backend (if
> the postmaster is started from a shell where coresize limit
> is unlimited you should find one in the database directory
> after the crash
>
> Hi Maarten,
>
> > Hi,
> >
> > I don't know about the crashes, but try using 'SELECT'
> > instead of 'SALACT' (where the hell did you get *that*
> > from??).
> >
>
> Well. I never tried SALACT. I wanted to express that if one would
> do so the backend would die abnormally on the HP-Ux system.
>
Hi Maarten,
> Hi,
>
> I don't know about the crashes, but try using 'SELECT'
> instead of 'SALACT' (where the hell did you get *that*
> from??).
>
Well. I never tried SALACT. I wanted to express that if one would
do so the backend would die abnormally on the HP-Ux system.
(On a Linux system
Hello everybody,
I trying to run PostgreSQL 6.4 (or 6.4.2) on a HP-Ux 10.10. The
problem is that the backend process is dieing after two SQL errors.
When I do the following the backend will die:
psql test
=> SALACT * FROM test;
Error
=> SALACT * FROM test;
Error
Well nobody is using
