pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a

pgsql: Force immediate commit after CREATE DATABASE etc in extended pro

2022-07-26 Thread Tom Lane
Force immediate commit after CREATE DATABASE etc in extended protocol. We have a few commands that "can't run in a transaction block", meaning that if they complete their processing but then we fail to COMMIT, we'll be left with inconsistent on-disk state. However, the existing defenses for this a