Re: TODO item: Allow more complex user/database default GUC settings

Tom Lane escribió:
> Gurjeet Singh <singh.gurjeet@gmail.com> writes:
> > ON instead of second ALTER looks better, and IMHO DATABASE <dbname> should
> > be optional too:
> 
> > ALTER ROLE <rolename> [ON DATABASE <dbname>] SET <config> TO <value>;
> 
> IN, not ON.

This creates a parser conflict with
CREATE ROLE foo IN ROLE bar

I think it can be solved by splitting OptRoleElem in a set of
productions for ALTER and a superset of that for ALTER.  I'll go try
that.

-- 
Alvaro Herrera                                http://www.CommandPrompt.com/
PostgreSQL Replication, Consulting, Custom Development, 24x7 support