Thank you all for your responses, sorry for the delay in replying.
Reading the threads, it appears to me that nobody has tried to reproduce the issue with the "CREATE DATABASE my_database WITH OWNER=my_user" on an AWS instance so I am still at a loss as to whether:
- I have hit a bug with the "CREATE DATABASE my_database WITH OWNER=my_user" command, in which case I am working around it by issuing an "ALTER DATABASE my_database OWNER TO my_user" command,
or
- I am exploiting a bug in the "ALTER DATABASE my_database OWNER TO my_user" command in which case I really should look at doing this another way.
As David J points out, both "CREATE DATABASE my_database WITH OWNER=my_user" and "ALTER DATABASE my_database OWNER TO my_user" should fail or both should succeed - I am seeing inconsistent behaviour on AWS where "CREATE DATABASE" fails whilst "ALTER DATABASE" succeeds.
Myka
The convention here is to in-line/bottom post.
On Wednesday, March 27, 2024, Andrey Lizenko <lizenko79@gmail.com> wrote:
Totally from scratch it works w\o rdsadmin:
Your test doesn’t include the failure mode command…create database with owner.
David J.