From: | Andres Freund <andres(at)anarazel(dot)de> |
---|---|
To: | Magnus Hagander <magnus(at)hagander(dot)net> |
Cc: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Daniel Gustafsson <daniel(at)yesql(dot)se> |
Subject: | Re: Online enabling of checksums |
Date: | 2018-02-22 19:41:15 |
Message-ID: | 20180222194115.nchwwotbngaolwof@alap3.anarazel.de |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)anarazel(dot)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
From | Date | Subject | |
---|---|---|---|
Next Message | Magnus Hagander | 2018-02-22 19:44:17 | Re: Online enabling of checksums |
Previous Message | Claudio Freire | 2018-02-22 19:33:53 | Re: Hash Joins vs. Bloom Filters / take 2 |