that your 15 install did not throw an error is probably a bug.
I do get an error in the latest 15, though, so perhaps this is one of
those that was fixed along the way. What exact 15.x version were you
running?
--
Álvaro Herrera 48°01'N 7°57'E — https://www.Enterpri
obably have lower overhead. But you may need to lock the table
explicitly to prevent concurrency problems.
--
Álvaro HerreraBreisgau, Deutschland — https://www.EnterpriseDB.com/
"Doing what he did amounts to sticking his fingers under the hood of the
implementation; if he gets his fingers burnt, it's his problem." (Tom Lane)
if that returns it to the original performance.
The new strategy is allegedly faster, but maybe in your case, for
whatever reason, it isn't.
I do wonder why is the database drop/create performance so critical,
though. I mean, surely there are more relevant performance problems to
be conc
ll Storey
Author: Nathan Bossart
Co-authored-by: Gurjeet Singh
Reviewed-by: Laurenz Albe
Reviewed-by: Fujii Masao
Reviewed-by: Robert Treat
Discussion: https://postgr.es/m/Z2DE4lDX4tHqNGZt%40dev.null
--
Álvaro Herrera PostgreSQL Developer — https://www.Ent
