mirror of
https://github.com/postgres/postgres.git
synced 2025-06-04 00:02:37 -04:00
Remove unnecessary semicolons after goto labels
According to the C standard, a label must followed by a statement. If there was ever a time we needed an empty statement here, it was a long time ago. Japin Li Reviewed by Julien Rouhaud Discussion: https://www.postgresql.org/message-id/MEYP282MB16690F40189A4F060B41D56DB65E9%40MEYP282MB1669.AUSP282.PROD.OUTLOOK.COM
This commit is contained in:
parent
357cfefb09
commit
6291b2546c
@ -1239,7 +1239,7 @@ SimpleLruTruncate(SlruCtl ctl, int cutoffPage)
|
||||
*/
|
||||
LWLockAcquire(shared->ControlLock, LW_EXCLUSIVE);
|
||||
|
||||
restart:;
|
||||
restart:
|
||||
|
||||
/*
|
||||
* While we are holding the lock, make an important safety check: the
|
||||
|
@ -1373,7 +1373,7 @@ ExecDelete(ModifyTableContext *context,
|
||||
* special-case behavior needed for referential integrity updates in
|
||||
* transaction-snapshot mode transactions.
|
||||
*/
|
||||
ldelete:;
|
||||
ldelete:
|
||||
result = ExecDeleteAct(context, resultRelInfo, tupleid, changingPart);
|
||||
|
||||
switch (result)
|
||||
@ -1855,7 +1855,7 @@ ExecUpdateAct(ModifyTableContext *context, ResultRelInfo *resultRelInfo,
|
||||
* then trigger.c will have done table_tuple_lock to lock the correct
|
||||
* tuple, so there's no need to do them again.)
|
||||
*/
|
||||
lreplace:;
|
||||
lreplace:
|
||||
|
||||
/* ensure slot is independent, consider e.g. EPQ */
|
||||
ExecMaterializeSlot(slot);
|
||||
@ -2686,7 +2686,7 @@ ExecMergeMatched(ModifyTableContext *context, ResultRelInfo *resultRelInfo,
|
||||
econtext->ecxt_innertuple = context->planSlot;
|
||||
econtext->ecxt_outertuple = NULL;
|
||||
|
||||
lmerge_matched:;
|
||||
lmerge_matched:
|
||||
|
||||
/*
|
||||
* This routine is only invoked for matched rows, and we must have found
|
||||
|
Loading…
x
Reference in New Issue
Block a user