Re: Help, server doesn't start

["Anibal David Acosta" <aa@xxxxxxxxxxxx>]

shared_preload_libraries changed to '', no more errors about this issue but server doesn’t start

 

So, reading some information I found that pg_resetxlog maybe solve the problem, and maybe some data will lose

 

I execute the pg_resetxlog and now everything is working, just god will know what I lose J, but due te importance of the service we decide this instead of a long service down

 

Thanks!

 

 

 

De: Craig Ringer [mailto:ringerc@xxxxxxxxxxxxx]
Enviado el: lunes, 25 de junio de 2012 12:54 a.m.
Para: Anibal David Acosta
CC: 'Raghavendra'; pgsql-general@xxxxxxxxxxxxxx
Asunto: Re: Help, server doesn't start

 

On 06/25/2012 12:40 PM, Anibal David Acosta wrote:

Yes, we must upgrade.

The value of the shared_preload_libraries is

 

shared_preload_libraries = '$libdir/plugins/plugin_debugger.dll'                               # (change requires restart)

Change that to:

shared_preload_libraries = ''

(two single quotes, not a double quote)

It's unlikely that the PL/PgSQL debugger plugin is the issue, but since it's repeated in your logs, it's worth a go.

 When I login into the server the disk used by Postgres installation was without space (0Bytes available).

 

OK, so you probably do just have xlogs that're cut short. So long as nobody tried to "fix" the problem by deleting things out of the PostgreSQL data directory I expect you'll be OK.

AFAIK Pg is supposed to recover gracefully from out-of-disk situations, but this _is_ quite an old version.

I wonder if there are any out-of-disk tests in the Pg unit tests? It'd be somewhat tricky to automate testing for, but really good to do if it's practical. Something for my bored-weekend TODO I guess, even if it's just a standalone test set.

Right now I am making a file-level copy of the entire postgres folder in order to run some corruption recover method

Great.

--
Craig Ringer