X-Original-To: pgsql-admin-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by svr1.postgresql.org (Postfix) with ESMTP id AE5E1D6FA0 for ; Tue, 8 Nov 2005 08:45:14 -0400 (AST) Received: from svr1.postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 75411-10 for ; Tue, 8 Nov 2005 12:45:11 +0000 (GMT) Received: from news.hub.org (news.hub.org [200.46.204.72]) by svr1.postgresql.org (Postfix) with ESMTP id 86FEAD6805 for ; Tue, 8 Nov 2005 08:45:13 -0400 (AST) Received: from news.hub.org (news.hub.org [200.46.204.72]) by news.hub.org (8.13.1/8.13.1) with ESMTP id jA8CjAA4077367 for ; Tue, 8 Nov 2005 12:45:10 GMT (envelope-from news@news.hub.org) Received: (from news@localhost) by news.hub.org (8.13.1/8.13.1/Submit) id jA8Cadwr074609 for pgsql-admin@postgresql.org; Tue, 8 Nov 2005 12:36:39 GMT (envelope-from news) From: MaXX X-Newsgroups: pgsql.admin Subject: Re: Moving pg_xlog problem Date: Tue, 08 Nov 2005 13:36:31 +0100 Organization: Service de news de lacave.net Lines: 18 Message-ID: References: <1131434492.31264.42.camel@Panoramix> <1131440219.31264.47.camel@Panoramix> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7Bit X-Complaints-To: abuse@lacave.net User-Agent: KNode/0.9.2 To: pgsql-admin@postgresql.org X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=-1.54 required=5 tests=[ALL_TRUSTED=-1.44, AWL=-0.100] X-Spam-Score: -1.54 X-Spam-Level: X-Archive-Number: 200511/60 X-Sequence-Number: 19433 Joost Kraaijeveld wrote: > On Mon, 2005-11-07 at 23:46 -0800, Jeff Frost wrote: >> So, what happens if you do this as the postgres user: >> ls -l /var/lib/postgresql/8.0/main/pg_xlog/ >> I'm going to guess the output indicates you have a directory inside >> pg_xlog called pg_xlog_orig. > Sorry, copied and pasted the wrong part of the history file: the > directory structure is OK as far as I can see, but there must something > wrong... I ran in the same problem a while before, Check permissions and how the symlink was created, it must be 'ln -s /full/path /full/dst/path' ,no './' ... That solved my problem... HTH, -- MaXX