Re: [PATCHES] Writing WAL for relcacheinvalidation:pg_internal.init

From: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
To: "Jerry Sievers" <jerry(at)jerrysievers(dot)com>
Cc: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: [PATCHES] Writing WAL for relcacheinvalidation:pg_internal.init
Date: 2006-11-02 14:44:24
Message-ID: 1162478664.3587.376.camel@silverbirch.site
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

On Thu, 2006-11-02 at 09:36 -0500, Jerry Sievers wrote:

> Is it safe to delete the .init files now (before starting recovery),
> or perhaps unconditionally right after going live?

You're safe to delete those files from the restored version of your base
backup prior to commencing startup with a recovery.conf.

When they are missing they will be recreated automatically.

When we agree on how to fix it, which should be soon, I would imagine
that the fix can be back patched to 8.0 and 8.1 and fixed prior to
release in 8.2.

--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2006-11-02 14:55:36 Re: Writing WAL for relcache invalidation:pg_internal.init
Previous Message Jerry Sievers 2006-11-02 14:36:10 Re: [PATCHES] Writing WAL for relcache invalidation:pg_internal.init

Browse pgsql-patches by date

  From Date Subject
Next Message Tom Lane 2006-11-02 14:55:36 Re: Writing WAL for relcache invalidation:pg_internal.init
Previous Message Jerry Sievers 2006-11-02 14:36:10 Re: [PATCHES] Writing WAL for relcache invalidation:pg_internal.init