Re: pg_stop_backup() v2 incorrectly marked as proretset

From: Michael Paquier <michael(at)paquier(dot)xyz>
To: Kyotaro Horiguchi <horikyota(dot)ntt(at)gmail(dot)com>
Cc: pgsql-hackers(at)lists(dot)postgresql(dot)org
Subject: Re: pg_stop_backup() v2 incorrectly marked as proretset
Date: 2022-03-02 10:04:17
Message-ID: Yh9BIWEcWVZJUQm1@paquier.xyz
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Mar 02, 2022 at 05:22:35PM +0900, Kyotaro Horiguchi wrote:
> But the patch forgets to remove an useless variable.

Indeed. I forgot to look at stderr.

>> /* Initialise attributes information in the tuple descriptor */
>> tupdesc = CreateTemplateTupleDesc(PG_STOP_BACKUP_V2_COLS);
>> TupleDescInitEntry(tupdesc, (AttrNumber) 1, "lsn",
>> PG_LSNOID, -1, 0);
>
> I think we can use get_call_resuilt_type here.

Yes, I don't mind doing so here.
--
Michael

Attachment Content-Type Size
stopbackup-no-srf-2.patch text/x-diff 3.8 KB

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dean Rasheed 2022-03-02 10:10:57 Re: [PATCH] Add reloption for views to enable RLS
Previous Message Aleksander Alekseev 2022-03-02 10:03:31 Re: create_index test fails when synchronous_commit = off @ master