Re: pg_stop_backup() v2 incorrectly marked as proretset - Mailing list pgsql-hackers

From Aleksander Alekseev
Subject Re: pg_stop_backup() v2 incorrectly marked as proretset
Date
Msg-id CAJ7c6TO2rq3LTe_TsPgb8RWuAnxd-gs0qV7g6HACu21P9cTXEQ@mail.gmail.com
Whole thread Raw
In response to Re: pg_stop_backup() v2 incorrectly marked as proretset  (Michael Paquier <michael@paquier.xyz>)
Responses Re: pg_stop_backup() v2 incorrectly marked as proretset  (Robert Haas <robertmhaas@gmail.com>)
List pgsql-hackers
Hi Michael,

```
 Datum
 pg_stop_backup_v2(PG_FUNCTION_ARGS)
 {
-    ReturnSetInfo *rsinfo = (ReturnSetInfo *) fcinfo->resultinfo;
+#define PG_STOP_BACKUP_V2_COLS 3
     TupleDesc    tupdesc;
-    Tuplestorestate *tupstore;
-    MemoryContext per_query_ctx;
-    MemoryContext oldcontext;
-    Datum        values[3];
-    bool        nulls[3];
+    Datum        values[PG_STOP_BACKUP_V2_COLS];
+    bool        nulls[PG_STOP_BACKUP_V2_COLS];
```

Declaring a macro inside the procedure body is a bit unconventional.
Since it doesn't seem to be used for anything except these two array
declarations I suggest keeping simply "3" here.

-- 
Best regards,
Aleksander Alekseev



pgsql-hackers by date:

Previous
From: Daniel Gustafsson
Date:
Subject: Re: psql: Make SSL info display more compact
Next
From: Amit Kapila
Date:
Subject: Re: Handle infinite recursion in logical replication setup