Skip site navigation (1) Skip section navigation (2)

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-01 18:15:42
Message-ID: 1162404943.3587.144.camel@silverbirch.site (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-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



In response to

pgsql-hackers by date

Next:From: Kai-Uwe SattlerDate: 2006-11-01 18:41:58
Subject: Re: [Fwd: Index Advisor]
Previous:From: Simon RiggsDate: 2006-11-01 17:20:26
Subject: Re: Extended protocol logging

pgsql-patches by date

Next:From: Simon RiggsDate: 2006-11-02 08:45:39
Subject: Re: Writing WAL for relcache invalidation:pg_internal.init
Previous:From: Simon RiggsDate: 2006-11-01 17:20:26
Subject: Re: Extended protocol logging

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group