Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

--On 27. Oktober 2015 14:07:06 + Kevin Grittner wrote: > It would be a boon to big shops if they could > declare (preferably with the option to set it at a role level) that > specific default_transaction_* settings could not be overridden. A while ago i was faced with

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

On Tuesday, October 27, 2015 10:57 PM, Muthiah Rajan wrote: > On 27-Oct-2015 7:37 PM, "Kevin Grittner" wrote: >> It is more problematic where a shop wants to use serializable >> transactions to ensure data integrity. > This may be a trivial thing But

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

On 2015/10/28 12:57, Muthiah Rajan wrote: > Hello Kevin, > > This may be a trivial thing But what do you mean by shops? I actually > can't get it :-) I think it's casually used to mean a company or a production environment. Thanks, Amit -- Sent via pgsql-hackers mailing list

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

Thanks Amit... :-) -- View this message in context: http://postgresql.nabble.com/Disabling-START-TRANSACTION-for-a-SuperUser-tp5871630p5871739.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

Thanks for clarifying my doubt... -- Muthiah Rajan On Wed, Oct 28, 2015 at 6:19 PM, Kevin Grittner wrote: > On Tuesday, October 27, 2015 10:57 PM, Muthiah Rajan > wrote: > > On 27-Oct-2015 7:37 PM, "Kevin Grittner" wrote: > > >> It

[HACKERS] Disabling START TRANSACTION for a SuperUser

Hi, I have created a readonly user by executing the following statements, CREATE USER backupadm SUPERUSER password 'mypass'; ALTER USER backupadm set default_transaction_read_only = on; But the backupadm user is able to create/update table when using START TRANSACTION READ WRITE and then

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

Hey Craig, Thanks for your response. Seems like the workaround is difficult. I am trying to understand " ExecutorStart_hook and ProcessUtility_hook, implemented with a C extension. You can find an example of one in pg_stat_statements, sepgsql, and in the BDR source code. The latter uses it

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

On 27 October 2015 at 18:25, rajan wrote: > Hi, > > I have created a readonly user by executing the following statements, > CREATE USER backupadm SUPERUSER password 'mypass'; A superuser can never be a read only user. > ALTER USER backupadm set default_transaction_read_only

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

Hello Kevin, This may be a trivial thing But what do you mean by shops? I actually can't get it :-) On 27-Oct-2015 7:37 PM, "Kevin Grittner" wrote: > On Tuesday, October 27, 2015 8:52 AM, Craig Ringer > wrote: > > On 27 October 2015 at 21:19,

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

Thanks Craig, There are a lot of details and its overwhelming :-) Let me digest and will post for any help On 27-Oct-2015 7:21 PM, "Craig Ringer" wrote: > On 27 October 2015 at 21:19, rajan <[hidden email] > > wrote:

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

On 27 October 2015 at 21:19, rajan wrote: > Hey Craig, > > Thanks for your response. Seems like the workaround is difficult. > > I am trying to understand > " > ExecutorStart_hook and ProcessUtility_hook Doing what you want will require being willing to spend a fair bit of

Re: [HACKERS] Disabling START TRANSACTION for a SuperUser

On Tuesday, October 27, 2015 8:52 AM, Craig Ringer wrote: > On 27 October 2015 at 21:19, rajan wrote: >> Thanks for your response. Seems like the workaround is difficult. >> >> I am trying to understand >> " >> ExecutorStart_hook and