On Mon, Jun 25, 2012 at 9:19 AM, Kevin Grittner
wrote:
> Mike Broers wrote:
>
>> Ultimately the hosting service restored the files that they had
>> not brought over during their maintenance migration and we started
>> up ok. So that was a relief.
>
> +1
>
>> We had archived log files but it did
Mike Broers wrote:
> Ultimately the hosting service restored the files that they had
> not brought over during their maintenance migration and we started
> up ok. So that was a relief.
+1
> We had archived log files but it did not appear that the archive
> destination was caught up with the
Ultimately the hosting service restored the files that they had not brought
over during their maintenance migration and we started up ok. So that was
a relief.
We had archived log files but it did not appear that the archive
destination was caught up with the xlog the cluster was complaining abou
On Sun, Jun 24, 2012 at 2:15 PM, Craig Ringer wrote:
> On 06/24/2012 03:45 AM, Kevin Grittner wrote:
>>
>> As previously stated, make sure you understand how this happened, so
>> you can make sure it doesn't happen again. The contents of the
>> pg_xlog directory are an integral part of your datab
On 06/24/2012 03:45 AM, Kevin Grittner wrote:
As previously stated, make sure you understand how this happened, so
you can make sure it doesn't happen again. The contents of the
pg_xlog directory are an integral part of your database cluster.
People not backing up pg_xlog, deleting its content
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
10 matches
Mail list logo