From: | Jacob Champion <champion(dot)p(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Aleksander Alekseev <aleksander(at)timescale(dot)com> |
Cc: | Stephen Frost <sfrost(at)snowman(dot)net>, Andrew Dunstan <andrew(at)dunslane(dot)net>, Akshat Jaimini <destrex271(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
Subject: | Re: pg_dump needs SELECT privileges on irrelevant extension table |
Date: | 2023-11-10 20:48:04 |
Message-ID: | CAGu=u8hz__hvQiQZT=EcD9G_jFhNiYj9UVBwSaSQ0BGC+6NzHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs pgsql-hackers |
On Thu, Nov 9, 2023 at 11:02 AM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> I'm hearing nothing but crickets :-(
Yeah :/
Based on your arguments above, it sounds like your patch may improve
several other corner cases when backported, so that sounds good
overall to me. My best guess is that Timescale will be happy with this
patch's approach. But I can't speak with any authority.
Aleks -- anything to add?
--Jacob
From | Date | Subject | |
---|---|---|---|
Next Message | Alexander Korotkov | 2023-11-10 21:02:11 | Re: BUG #18187: Unexpected error: "variable not found in subplan target lists" triggered by JOIN |
Previous Message | PG Bug reporting form | 2023-11-10 19:47:30 | BUG #18190: PL/pgSQL does not document comparison operations on RECORD (or ROW) types |
From | Date | Subject | |
---|---|---|---|
Next Message | Nathan Bossart | 2023-11-10 20:51:28 | locked reads for atomics |
Previous Message | Nathan Bossart | 2023-11-10 20:44:25 | Re: Adding facility for injection points (or probe points?) for more advanced tests |