Want to Move Your Redshift Groups, Users and Assign Them As You Did in Another DB
# spool this stuff to a file from your source db, then run the spooled SQL on your destination db […]
# spool this stuff to a file from your source db, then run the spooled SQL on your destination db […]
Redshift is based on a version of PostgreSQL that only allows SuperUsers to see pg_catalog objects. Here is a way
Analyzing How Your Redshift Cluster is Performing Queries and Storing Data Useful Queries Space Used – careful this shows total
https://aws.amazon.com/blogs/big-data/federate-database-user-authentication-easily-with-iam-and-amazon-redshift/
The following WLM properties are dynamic: Enable short query acceleration Maximum run time for short queries Concurrency Percent of memory
Some of this is a repeat for my own value from another of my blog posts – excuse my dust…
Coming from an Oracle background where schemas are roughly equivalent to owners the important differences between users, owners, and schemas
select * from pg_user_info where usename like ‘mcost%’; create user mcost with createuser password ‘1234Mike’; create user mcost1 with password
Here are SOME links to some psql features: http://www.postgresqltutorial.com/psql-commands/ http://www.postgresqltutorial.com/postgresql-list-users/ http://www.postgresqltutorial.com/postgresql-describe-table/ The most current PostgreSQL docs. as of 09/10/2018 –
Here is some of the material I used to prepare for the Amazon AWS Big Data Specialty Certification test Lets