Hello.
I think I may have found a bug in the CREATE USER MAPPING / DROP SERVER
handling.
It is possible to create a user mapping on a server and drop said server in
two concurrent transactions, and have both succeed.
This results in an orphan row in the pg_user_mapping table.
I would expect o
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the response.
How will this bug be handled with regards to releases ?
If the fix is going to take a while to be released, we could rename
our servers to valid names but we would prefer not to.
Regards,
- --
Ronan Dunklau
-BEGIN PGP
; (
col1 integer
)
SERVER file-test
OPTIONS (filename '/tmp/test');
Please look at the attached test case and the proposed patch.
Thank you.
--
Ronan Dunklau
create database test_dump_foreign_server;
\connect test_dump_foreign_server ;
create extension file_fdw;
create server &q
