Marcin <[EMAIL PROTECTED]> writes:
> Okay, then pg_filedump 1262:
> and suddenly:
> Block4
> -
> Block Offset: 0x8000 Offsets: Lower 0 (0x)
> Block: Size0 Version0Upper 0 (0x)
>
Marcin <[EMAIL PROTECTED]> writes:
> Yesterday morning one of our PostgreSQL engines stopped unexpectedly,
> [ with SIGSEGV at ]
> (gdb) bt
> #0 0x081b4e79 in GetRawDatabaseInfo ()
> #1 0x081b4865 in InitPostgres ()
> #2 0x08154741 in PostgresMain ()
This suggests corrupted data in pg_database,
On Mon, 2005-01-24 at 11:45, Marcin wrote:
> Hi,
> Yesterday morning one of our PostgreSQL engines stopped unexpectedly,
> with the following log:
>
> postgres[4192]: [5105-1] LOG: server process (PID 26678) was terminated by
> signal 11
Have you tried backing up your data directory (as a preca
Hi,
Yesterday morning one of our PostgreSQL engines stopped unexpectedly,
with the following log:
postgres[4192]: [5105-1] LOG: server process (PID 26678) was terminated by
signal 11
postgres[4192]: [5106-1] LOG: terminating any other active server processes
postgres[4192]: [5107-1] LOG: all s
