| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org>, Bruce Momjian <bruce(at)momjian(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Checking for missing heap/index files |
| Date: | 2022-10-19 14:20:20 |
| Message-ID: | CA+TgmoYMieMoQS8GxK3cSjeBqFRvcdwqjrR9B5zX+BcTRB=1eA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Oct 18, 2022 at 5:44 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> My concern about that is that it implies touching a whole lot of
> places, and if you miss even one then you've lost whatever guarantee
> you thought you were getting. More, there's no easy way to find
> all the relevant places (some will be in extensions, no doubt).
*scratches head*
I must be missing something. It seems to me that it requires touching
exactly the same set of places as your idea. And it also seems to me
like it's not that many places. Am I being really dumb here?
It's still somewhat unclear to me whether we should be doing anything
at all here.
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2022-10-19 14:40:21 | Re: Avoid memory leaks during base backups |
| Previous Message | Robert Haas | 2022-10-19 13:57:03 | Re: allowing for control over SET ROLE |