Zach Marine

Hey Ricky, greetings from Ethiopia. :) That makes sense to me and seems reasonable. Any interest in taking a shot at implementing this? A quick search makes it look like...

@sl33t Yeah, it looks like it may be as simple as that. I believe we just add it as a parameter to the .create() method [here](https://github.com/Squarespace/datasheets/blob/master/datasheets/workbook.py#L101) based on the [Drive...

Hey Ross, greetings from the other side. :) Yeah, this is a known bug and is recorded in issue #7. As a result, I'm closing this issue as a duplicate....

Hey Ross, that makes some sense to me. My one concern is whether you could then end up in a state where `pgbedrock configure` operates on a spec that can't...

Hey Harlan, that's a great request! My understanding is that the best way to verify whether something works with redshift is to test against Postgres 8.0. Do you have any...

After poking around a bit more, it looks like Redshift _does_ support default privileges as per AWS's documentation [here](https://docs.aws.amazon.com/redshift/latest/dg/r_ALTER_DEFAULT_PRIVILEGES.html), yet Postgres 8.0.2 definitely does not. First, the Postgres [release notes](https://bucardo.org/postgres_all_versions.html)...

Hey Harlan, I looked around a bit and it seems like people just create another redshift instance and test on that, so that seems like the best path forward. I'm...

Interesting. So it looks like it's missing three tables that pgbedrock uses: - `pg_roles` - this doesn't really need to be used; we should just swap out the one reference...

@cboline's suggestion is that we have a list of objects that pgbedrock will just ignore, so that's one possibility.

The issue with this is that the changes that each pgbedrock module determines are influenced by the changes that the prior modules make. For example, the `analyze_privileges` module runs last...