mirrors/postgres
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix code indentation violations introduced by recent commit

Browse Source 
The two culprit commits are 5765cfe and 5e0c761.

Per buildfarm member koel for the first commit, while I have noticed the
second one in passing.
This commit is contained in:
Michael Paquier 2023-08-11 20:43:34 +09:00
parent 5765cfe18c
commit 5dc456b7dd
3 changed files with 15 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

1
src/backend/utils/fmgr/fmgr.c
View File

@ -670,6 +670,7 @@ fmgr_security_definer(PG_FUNCTION_ARGS)
if (!isnull) if (!isnull)
{ {
ArrayType *array; ArrayType *array;
oldcxt = MemoryContextSwitchTo(fcinfo->flinfo->fn_mcxt); oldcxt = MemoryContextSwitchTo(fcinfo->flinfo->fn_mcxt);
array = DatumGetArrayTypeP(datum); array = DatumGetArrayTypeP(datum);
TransformGUCArray(array, &fcache->configNames, TransformGUCArray(array, &fcache->configNames,

2
src/bin/pgbench/pgbench.c
View File

@ -2246,7 +2246,7 @@ evalStandardFunc(CState *st,
* This value is double braced to workaround GCC bug 53119, which seems to * This value is double braced to workaround GCC bug 53119, which seems to
* exist at least on gcc (Debian 4.7.2-5) 4.7.2, 32-bit. * exist at least on gcc (Debian 4.7.2-5) 4.7.2, 32-bit.
*/ */
PgBenchValue vargs[MAX_FARGS] = { { 0 } }; PgBenchValue vargs[MAX_FARGS] = {{0}};
for (nargs = 0; nargs < MAX_FARGS && l != NULL; nargs++, l = l->next) for (nargs = 0; nargs < MAX_FARGS && l != NULL; nargs++, l = l->next)
{ {