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

Re: Writing WAL for relcache invalidation:pg_internal.init

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Simon Riggs" <simon(at)2ndquadrant(dot)com>
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 23:42:27
Message-ID: 26101.1162770147@sss.pgh.pa.us (view raw or flat)
Thread:
Lists: pgsql-hackerspgsql-patches
"Simon Riggs" <simon(at)2ndquadrant(dot)com> writes:
> 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.

Applied to HEAD and 8.1.  It doesn't work in 8.0 though, because
flatfiles.c doesn't exist.  AFAIR there isn't any startup-time scan
of pg_database at all before 8.1.  Not sure if it's worth coming up
with a whole new patch for that branch.

			regards, tom lane

In response to

pgsql-hackers by date

Next:From: Neil ConwayDate: 2006-11-05 23:43:05
Subject: Re: ldap: fix resource leak
Previous:From: Guillaume LelargeDate: 2006-11-05 22:47:32
Subject: Re: NULL in arrays

pgsql-patches by date

Next:From: Neil ConwayDate: 2006-11-05 23:43:05
Subject: Re: ldap: fix resource leak
Previous:From: Andrew DunstanDate: 2006-11-05 22:25:49
Subject: Re: WIP 2 interpreters for plperl

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