Re: Writing WAL for relcache invalidation:pg_internal.init

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-05 22:03:48
Message-ID: 1162764229.3587.941.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 ...

Patch enclosed.

Clean apply to HEAD, make check OK, plus restart check.
No specific PITR test, since same code path.

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

Attachment Content-Type Size
unlink_pg_internal_at_startup.patch text/x-patch 6.9 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew Dunstan 2006-11-05 22:25:49 Re: WIP 2 interpreters for plperl
Previous Message Tom Lane 2006-11-05 21:44:43 Re: Proposal: vacuum and autovacuum parameters tocontrol freezing

Browse pgsql-patches by date

  From Date Subject
Next Message Andrew Dunstan 2006-11-05 22:25:49 Re: WIP 2 interpreters for plperl
Previous Message Tom Lane 2006-11-05 21:44:43 Re: Proposal: vacuum and autovacuum parameters tocontrol freezing