Re: A patch for get origin from commit_ts. - Mailing list pgsql-hackers

From movead.li@highgo.ca
Subject Re: A patch for get origin from commit_ts.
Date
Msg-id 202007061112287118394@highgo.ca
Whole thread Raw
In response to A patch for get origin from commit_ts.  ("movead.li@highgo.ca" <movead.li@highgo.ca>)
Responses Re: A patch for get origin from commit_ts.  (Michael Paquier <michael@paquier.xyz>)
List pgsql-hackers

>+SELECT pg_replication_origin_create('test_commit_ts: get_origin_1');
>+SELECT pg_replication_origin_create('test_commit_ts: get_origin_2');
>+SELECT pg_replication_origin_create('test_commit_ts: get_origin_3');
>
>Why do you need three replication origins to test three times the same
>pattern?  Wouldn't one be enough and why don't you check after the
>timestamp?  I would also two extra tests: one with a NULL input and an
>extra one where the data could not be found.
> 
>+   found = TransactionIdGetCommitTsData(xid, &ts, &nodeid);
>+
>+   if (!found)
>+       PG_RETURN_NULL();
> 
>This part also looks incorrect to me, I think that you should still
>return two tuples, both marked as NULL.  You can do that just by
>switching the nulls flags to true for the two values if nothing can be
>found.
Thanks for the points and follow them, new patch attached.


Regards,
Highgo Software (Canada/China/Pakistan)
URL : www.highgo.ca
EMAIL: mailto:movead(dot)li(at)highgo(dot)ca
Attachment

pgsql-hackers by date:

Previous
From: torikoshia
Date:
Subject: Re: Creating a function for exposing memory usage of backend process
Next
From: Amul Sul
Date:
Subject: Re: Cleanup - adjust the code crossing 80-column window limit