From: | "Simon Riggs" <simon(at)2ndquadrant(dot)com> |
---|---|
To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | <pgsql-hackers(at)postgresql(dot)org>, <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: Writing WAL for relcache invalidation:pg_internal.init |
Date: | 2006-11-01 18:15:42 |
Message-ID: | 1162404943.3587.144.camel@silverbirch.site |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers pgsql-patches |
On Wed, 2006-11-01 at 12:05 -0500, Tom Lane wrote:
> I think we're probably better off to just forcibly remove the init file
> during post-recovery cleanup. The easiest place to do this might be
> BuildFlatFiles, which has to scan pg_database anyway ...
Presumably not rebuilding it, since we can let that occur naturally.
I'll submit a patch tomorrow.
--
Simon Riggs
EnterpriseDB http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Kai-Uwe Sattler | 2006-11-01 18:41:58 | Re: [Fwd: Index Advisor] |
Previous Message | Simon Riggs | 2006-11-01 17:20:26 | Re: Extended protocol logging |
From | Date | Subject | |
---|---|---|---|
Next Message | Simon Riggs | 2006-11-02 08:45:39 | Re: Writing WAL for relcache invalidation:pg_internal.init |
Previous Message | Simon Riggs | 2006-11-01 17:20:26 | Re: Extended protocol logging |