Sasha Krassovsky 89275f6c1e Fix invalid database resulting from failed DROP DB (#5423) ...

## Problem
If the control plane happened to respond to a DROP DATABASE request with
a non-200 response, we'd abort the DROP DATABASE transaction in the
usual spot. However, Postgres for some reason actually performs the drop
inside of `standard_ProcessUtility`. As such, the database was left in a
weird state after aborting the transaction. We had test coverage of a
failed CREATE DATABASE but not a failed DROP DATABASE.
 
## Summary of changes
Since DROP DATABASE can't be inside of a transaction block, we can just
forward the DDL changes to the control plane inside of
`ProcessUtility_hook`, and if we respond with 500 bail out of
`ProcessUtility` before we perform the drop. This change also adds a
test, which reproduced the invalid database issue before the fix was
applied.

2023-09-29 19:39:28 +01:00

..

hnsw

Forbid installation of hnsw extension (#5346)

2023-09-23 16:47:57 +01:00

neon

Fix invalid database resulting from failed DROP DB (#5423)

2023-09-29 19:39:28 +01:00

neon_rmgr

Feat/postgres 16 (#4761)

2023-09-12 15:11:32 +02:00

neon_test_utils

Feat/postgres 16 (#4761)

2023-09-12 15:11:32 +02:00

neon_utils

Be able to get number of CPUs (#3774)

2023-03-10 19:00:20 +02:00

neon_walredo

Feat/postgres 16 (#4761)

2023-09-12 15:11:32 +02:00

typedefs.list

Refotmat pgxn code, add typedefs.list that was used

2022-09-14 08:14:05 +03:00