Thank you for the PR, nicely done! If you intend to format an existing piece of code, please do so in a standalone Format code commit, such that feature additions will not be mixed together.

Thank you for the PR, nicely done! If you intend to format an existing piece of code, please do so in a standalone Format code commit, such that feature additions will not be mixed together.

Yep, that makes sense. Will avoid just running cargo fmt in future. I've added the RENAME VALUE statement as well. I just realised I accidentally PR'd from my fork's master instead of the add_alter_type feature branch, sorry about that!

---- src/extension/postgres/types.rs - extension::postgres::types::TypeAlterStatement::name (line 308) stdout ----
Test executable failed (exit code 101).

stderr:
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `"ALTER TYPE \"font_family\" ADD VALUE \'cursive\'"`,
 right: `"ALTER TYPE \"font_family\" ADD VALUE \'cursive\' "`', src/extension/postgres/types.rs:24:1
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

The test fails because of the extra space at the end of the assert.
You can run all test cases (including doc tests by running)

cargo test --doc --all-features

I missed that! Thanks

Looks good to me! Ready for merging?

I intentionally ran cargo fmt on my branch to 'subtract out' those lines.