Re: Extend ALTER DEFAULT PRIVILEGES for large objects

From: Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>
To: Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com>
Cc: Laurenz Albe <laurenz(dot)albe(at)cybertec(dot)at>, Nathan Bossart <nathandbossart(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Extend ALTER DEFAULT PRIVILEGES for large objects
Date: 2025-07-16 07:22:31
Message-ID: 20250716162231.c5d135012174959b7b482aa2@sraoss.co.jp
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Tue, 15 Jul 2025 19:07:16 +0900
Fujii Masao <masao(dot)fujii(at)oss(dot)nttdata(dot)com> wrote:

> I've pushed the patch. Thanks!

Thank you!

>
> >>> But perhaps this corner case doesn't really
> >>> need to be handled?
> >>
> >> Probably I failed to get your point here. Could you clarify what you meant?
> >
> > I'm sorry for not explaining it clearly.
> >
> > Currently, TO or FROM could be suggested immediately after FOREIGN SERVER, but
> > only when no foreign servers are defined. When foreign servers do exist,
> > their names are correctly suggested instead, as expected.
> >
> > The patch fixed the behavior so that TO or FROM are not suggested after FOREIGN SERVER,
> > even when no foreign servers are defined. However, I've started to wonder if it's worth
> > fixing such a corner case. What do you think?
>
> I think it's worth doing. This issue can lead to unexpected behavior
> and is something users might run into. If the fix were overly complex
> for a minor issue, it might not be justified. But that's not the case here.

Thank you for your explanation.
It makes sense to me.

Regards,
Yugo Nagata

--
Yugo Nagata <nagata(at)sraoss(dot)co(dot)jp>

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Tomas Vondra 2025-07-16 08:40:29 Re: index prefetching
Previous Message Joel Jacobson 2025-07-16 07:00:05 Re: Optimize LISTEN/NOTIFY