[HACKERS] Need help on pgcrypto

Trying to find a documentation which will make me understand how to secure a password column. I want the encryption to be one way and it should not be decrypted. I am able to find discrete documents but nothing of them gets me there. Please help. - -- Thanks, Rajan. -- View this message

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 is more problematic wher

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

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, rajan wr

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] > <http:///user/SendEmail.jtp?type=node&node=5871647&

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 for

[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 COMMIT;

Re: [HACKERS] SuperUser check in pg_stat_statements

Hey Lukas, Thanks. Able to see the queries from all users. Can you explain the monitoring.get_stat_statements()? -- View this message in context: http://postgresql.nabble.com/SuperUser-check-in-pg-stat-statements-tp5870589p5870733.html Sent from the PostgreSQL - hackers mailing list archive at

Re: [HACKERS] SuperUser check in pg_stat_statements

Jim, I already tried to create a view upon the pg_stat_statements, but no luck. -- View this message in context: http://postgresql.nabble.com/SuperUser-check-in-pg-stat-statements-tp5870589p5870683.html Sent from the PostgreSQL - hackers mailing list archive at Nabble.com. -- Sent via pgsql

Re: [HACKERS] SuperUser check in pg_stat_statements

Thanks Stephen and Shulgin for your response. Will go through the patch and will try to solve my problem using that. My scenario is that i need to have an user who cannot be a super user but a monitor user, who will be able to see all the queries executed by all users. -- View this message in

[HACKERS] SuperUser check in pg_stat_statements

Hello, When monitoring using pg_stat_satements I see that postgres by default conceals queries executed by other users from the user who is selecting the pg_stat_statements view. I have edited the pg_stat_statements.c by disabling the superuser check function so that all queries will be visible t