Re: Standalone backends run StartupXLOG in an incorrect environment - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Standalone backends run StartupXLOG in an incorrect environment
Date
Msg-id 17070.1271696464@sss.pgh.pa.us
Whole thread Raw
In response to Re: Standalone backends run StartupXLOG in an incorrect environment  (Simon Riggs <simon@2ndQuadrant.com>)
List pgsql-hackers
Simon Riggs <simon@2ndQuadrant.com> writes:
> On Mon, 2010-04-19 at 11:19 -0400, Tom Lane wrote:
>> If you think we're at the point where this item is the main thing
>> standing between us and beta, I'll go do something about it.  I've
>> been waiting for the HS code to settle before trying to design a
>> solution...

> I'm not hugely interested in supporting HS in standalone backends.

I'm not either.  The type of scenario that I'm worried about is someone
trying to use a standalone backend to clean up after a recovery failure.
Right now I'm afraid that could make things worse (ie create additional
corruption).
        regards, tom lane


pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: idle in txn query cancellation
Next
From: Tom Lane
Date:
Subject: Re: cost_rescan (was: match_unsorted_outer() vs. cost_nestloop())