Yes, we must upgrade. The value of the shared_preload_libraries is shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll' # (change requires restart) An additional information…. When I login into the server the disk used by Postgres installation was without space (0Bytes available). Also is possible that someone (I am checking now) restart the Postgres service in the middle of this situation Right now I am making a file-level copy of the entire postgres folder in order to run some corruption recover method Thanks! De: Raghavendra [mailto:raghavendra.rao@enterprisedb.com] On Mon, Jun 25, 2012 at 8:23 AM, Anibal David Acosta <aa@xxxxxxxxxxxx> wrote: We have an old postgres installation (8.3) running on windows 2003 The server run perfect for many years but today it crash L We have a very old backup so I’ll try desperate to repair. If I can’t repair I want to skip the error and start server with only healthy data, no matter if I lose some table page, entire table or even entire database because the server has many databases inside. Side-by, you should also consider upgrading PG versions to latest.
Can you also paste whats there in shared_preload_libraries setting from $PGDATA/postgresql.conf ? --- |