Re: Should SET ROLE inherit config params?

Bruce Momjian <bruce@momjian.us>

From: Bruce Momjian <bruce@momjian.us>
To: Josh Berkus <josh@agliodbs.com>
Cc: Simon Riggs <simon@2ndQuadrant.com>, Tom Lane <tgl@sss.pgh.pa.us>, Greg Stark <stark@enterprisedb.com>, pgsql-hackers@postgresql.org
Date: 2009-03-28T03:25:29Z
Lists: pgsql-hackers

Attachments

Josh Berkus wrote:
> 
> > Josh, this isn't a rejection. Both Tom and I asked for more exploration
> > of the implications of doing as you suggest. Tom has been more helpful
> > than I was in providing some scenarios that would cause problems. It is
> > up to you to solve the problems, which is often possible. 
> 
> OK, well, barring the context issues, what do people think of the idea?
> 
> What I was thinking was that this would be a setting on the SET ROLE 
> statement, such as:
> 
> SET ROLE special WITH SETTINGS
> 
> ... or similar; I'd need to find an existing keyword which works.
> 
> I think this bypasses a lot of the issues which Tom raises, but I'd want 
> to think about the various permutations some more.

I have added the following TODO:

	Allow role-specific ALTER ROLE SET variable settings to be processed
	independently of login; SET ROLE does not process role-specific variable
	settings
	
	    * http://archives.postgresql.org/message-id/49B82CD7.20802@agliodbs.com 

and the attached patch which better documents our current behavior.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

  + If your life is a hard drive, Christ can be your backup. +