From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
---|---|
To: | Robert Haas <robertmhaas(at)gmail(dot)com> |
Cc: | Andres Freund <andres(at)anarazel(dot)de>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org>, Dilip Kumar <dilipbalaut(at)gmail(dot)com> |
Subject: | Re: wrong fds used for refilenodes after pg_upgrade relfilenode changes Reply-To: |
Date: | 2022-05-11 06:04:07 |
Message-ID: | CA+hUKG+AUQAm3pm+WFQNCv2LU0w+v9z0iozicdYVn_wmfy6=Rg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Tue, May 10, 2022 at 1:07 AM Robert Haas <robertmhaas(at)gmail(dot)com> wrote:
> On Sun, May 8, 2022 at 7:30 PM Thomas Munro <thomas(dot)munro(at)gmail(dot)com> wrote:
> > LOG: still waiting for pid 1651417 to accept ProcSignalBarrier
> > STATEMENT: alter database mydb set tablespace ts1;
> This is a very good idea.
OK, I pushed this, after making the ereport call look a bit more like
others that talk about backend PIDs.
> > Another thought is that it might be nice to be able to test with a
> > dummy PSB that doesn't actually do anything. You could use it to see
> > how fast your system processes it, while doing various other things,
> > and to find/debug problems in other code that fails to handle
> > interrupts correctly. Here's an attempt at that. I guess it could go
> > into a src/test/modules/something instead of core, but on the other
> > hand the PSB itself has to be in core anyway, so maybe not. Thoughts?
> > No documentation yet, just seeing if people think this is worth
> > having... better names/ideas welcome.
>
> I did this at one point, but I wasn't convinced it was going to find
> enough bugs to be worth committing. It's OK if you're convinced of
> things that didn't convince me, though.
I'll leave this here for now.
From | Date | Subject | |
---|---|---|---|
Next Message | Ajin Cherian | 2022-05-11 06:21:59 | Re: Support logical replication of DDLs |
Previous Message | Michael Paquier | 2022-05-11 05:42:26 | Re: Allowing REINDEX to have an optional name |