public inbox for [email protected]  

help / color / mirror / Atom feed

From: Yugo Nagata <[email protected]>
To: Fujii Masao <[email protected]>
Cc: Laurenz Albe <[email protected]>
Cc: Nathan Bossart <[email protected]>
Cc: Tom Lane <[email protected]>
Cc: [email protected]
Subject: Re: Extend ALTER DEFAULT PRIVILEGES for large objects
Date: Wed, 11 Jun 2025 13:57:37 +0900
Message-ID: <[email protected]> (raw)
In-Reply-To: <[email protected]>
References: <[email protected]>
	<[email protected]>
	<20240424210839.GA863220@nathanxps13>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>
	<[email protected]>

On Wed, 11 Jun 2025 13:33:07 +0900
Fujii Masao <[email protected]> wrote:

> 
> 
> On 2025/06/11 11:49, Yugo Nagata wrote:
> > While looking at the thread [1], I've remembered this thread.
> > The patches in this thread are partially v18-related, but include
> > enhancement or fixes for existing feature, so should they be postponed
> > to v19, or should be separated properly to v18 part and other?
> > 
> > [1] https://www.postgresql.org/message-id/70372bdd-4399-4d5b-ab4f-6d4487a4911a%40oss.nttdata.com
> 
> I see these patches more as enhancements to psql tab-completion,
> rather than fixes for clear oversights in the original commit.
> 
> For example, if tab-completion for ALTER DEFAULT PRIVILEGES had
> completely missed LARGE OBJECTS, that would be an obvious oversight.
> But these patches go beyond that kind of issue.
> 
> That said, if others think it's appropriate to include them in v18
> for consistency or completeness, I'm fine with that.
> 
> Regarding the 0002 patch:
> 
> -	else if (Matches("GRANT", MatchAnyN, "ON", MatchAny, MatchAny))
> -		COMPLETE_WITH("TO");
> -	else if (Matches("REVOKE", MatchAnyN, "ON", MatchAny, MatchAny))
> -		COMPLETE_WITH("FROM");
> +	else if (Matches("GRANT/REVOKE", MatchAnyN, "ON", MatchAny, MatchAny))
> +	{
> +		if (TailMatches("FOREIGN", "SERVER"))
> +			COMPLETE_WITH_QUERY(Query_for_list_of_servers);
> +		else if (!TailMatches("LARGE", "OBJECT"))
> +		{
> +			if (Matches("GRANT", MatchAnyN, "ON", MatchAny, MatchAny))
> +				COMPLETE_WITH("TO");
> +			else
> +				COMPLETE_WITH("FROM");
> +		}
> +	}
> 
> Wouldn't this change break the case where "GRANT ... ON TABLE ... <TAB>"
> is supposed to complete with "TO"?

Sorry, I made a stupid mistake.

> +	else if (Matches("GRANT/REVOKE", MatchAnyN, "ON", MatchAny, MatchAny))

This should be "GRANT|REVOKE".

I've attached update patches. (There is no change on 0001.)

Best regards,
Yugo Nagata

-- 
Yugo Nagata <[email protected]>

view thread (33+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: Extend ALTER DEFAULT PRIVILEGES for large objects
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox