A follow up --
<...>
>>> a) quickly relieve the immediate pain
>>
>> Set autovacuum_cost_limit to a smaller value. (Change the
>> postgresql.conf file and do a reload.) I would start by cutting the
>> current value in half.
>> >
>Thanks -- would not have known how to start. But for now, in
Mike Broers wrote:
> Mike Broers wrote:
>> We shut down our postgres 8.3 server last night cleanly for some
>> hosted services maintenance. When we got our server back, it didnt
>> have the pg_xlog mount with files and now when we start the
>> server, it complains
>> Since we had a clean shut
On Sat, Jun 23, 2012 at 07:01:08AM -0500, Mike Broers wrote:
> Hello,
>
> We shut down our postgres 8.3 server last night cleanly for some hosted
> services maintenance. When we got our server back, it didnt have the
> pg_xlog mount with files
what happened to make the files not available? Seem
>
> 2012-06-23 06:06:04 CDT [18612]: [2-1] user=,db= LOG: could not open file
> "pg_xlog/00010A010040" (log file 2561, segment 64): No such
> file or
> directory
Don't do pg_resetlogs. If you have archives, please find for the file which
has pointed in logs copy it to $PGDATA/pg_xlo
I was able to duplicate the error in a test environment and get the
database started back up wtih the pg_resetxlog $PGDATA command, but i am
concerned about the fallout and not sure if i need to use any of the option
switches. We also have archived log files up to the point of server
shutdown if t
Hello,
We shut down our postgres 8.3 server last night cleanly for some hosted
services maintenance. When we got our server back, it didnt have the
pg_xlog mount with files and now when we start the server, it complains:
2012-06-23 06:06:04 CDT [18612]: [1-1] user=,db= LOG: database system was
