aboutsummaryrefslogtreecommitdiff
path: root/src/backend/access/transam/README.parallel
diff options
context:
space:
mode:
Diffstat (limited to 'src/backend/access/transam/README.parallel')
-rw-r--r--src/backend/access/transam/README.parallel2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/access/transam/README.parallel b/src/backend/access/transam/README.parallel
index db9ac3d504d..4d98f4e65d1 100644
--- a/src/backend/access/transam/README.parallel
+++ b/src/backend/access/transam/README.parallel
@@ -154,7 +154,7 @@ parallelism was started before all parallel workers have exited; and it's even
more clearly crazy for a parallel worker to try to subcommit or subabort the
current subtransaction and execute in some other transaction context than was
present in the initiating backend. It might be practical to allow internal
-sub-transactions (e.g. to implement a PL/pgsql EXCEPTION block) to be used in
+sub-transactions (e.g. to implement a PL/pgSQL EXCEPTION block) to be used in
parallel mode, provided that they are XID-less, because other backends
wouldn't really need to know about those transactions or do anything
differently because of them. Right now, we don't even allow that.