Avoid unnecessary table open/close in TRUNCATE command.
authorFujii Masao <fujii@postgresql.org>
Sun, 11 Apr 2021 15:05:58 +0000 (00:05 +0900)
committerFujii Masao <fujii@postgresql.org>
Sun, 11 Apr 2021 15:05:58 +0000 (00:05 +0900)
commit81a23dd87999ec9fb62554328c69c5b678612d56
tree5814b6ed1413e5cfa2c5658e91abc3a55a34cb15
parent08aa89b326261b669648df97d4f2a6edba22d26a
Avoid unnecessary table open/close in TRUNCATE command.

ExecuteTruncate() filters out the duplicate tables specified
in the TRUNCATE command, for example in the case where "TRUNCATE foo, foo"
is executed. Such duplicate tables obviously don't need to be opened
and closed because they are skipped. But previously it always opened
the tables before checking whether they were duplicated ones or not,
and then closed them if they were. That is, the duplicated tables were
opened and closed unnecessarily.

This commit changes ExecuteTruncate() so that it opens the table
after it confirms that table is not duplicated one, which leads to
avoid unnecessary table open/close.

Do not back-patch because such unnecessary table open/close is not
a bug though it exists in older versions.

Author: Bharath Rupireddy
Reviewed-by: Amul Sul, Fujii Masao
Discussion: https://postgr.es/m/CALj2ACUdBO_sXJTa08OZ0YT0qk7F_gAmRa9hT4dxRcgPS4nsZA@mail.gmail.com
src/backend/commands/tablecmds.c