Re: Online enabling of checksums - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Online enabling of checksums
Date
Msg-id 20180222194115.nchwwotbngaolwof@alap3.anarazel.de
Whole thread Raw
In response to Re: Online enabling of checksums  (Magnus Hagander <magnus@hagander.net>)
Responses Re: Online enabling of checksums
List pgsql-hackers
Hi,

On 2018-02-22 20:30:52 +0100, Magnus Hagander wrote:
> On Thu, Feb 22, 2018 at 8:24 PM, Andres Freund <andres@anarazel.de> wrote:
> > I suspect I'm going to get some grief for this, but I think the time has
> > come to bite the bullet and support changing databases in the same
> > process...
> >
> 
> Hey, I can't even see the goalposts anymore :P

Hah. I vote for making this a hard requirement :P


> Are you saying this should be done *in general*, or specifically for
> background workers? I'm assuming you mean the general case?

I'd say bgworkers first. It's a lot clearer how to exactly do it
there. Refactoring the mainloop handling in PostgresMain() would be a
bigger task.


> That would be very useful, but is probably a fairly non-trivial task
> (TM).

I'm not actually that sure it is. We have nearly all the code, I
think. Syscache inval, ProcKill(), and then you're nearly ready to do
the normal connection dance again.

Greetings,

Andres Freund


pgsql-hackers by date:

Previous
From: Claudio Freire
Date:
Subject: Re: Hash Joins vs. Bloom Filters / take 2
Next
From: Magnus Hagander
Date:
Subject: Re: Online enabling of checksums