On Tue, Mar 30, 2021 at 5:34 AM Peter Smith <smithpb2250@gmail.com> wrote:
>
> Please find attached the latest patch set v68*
>
> Differences from v67* are:
>
> * Rebased to HEAD @ today.
>
> * v68 fixes an issue reported by Vignesh [1] where a scenario was
> found which still was able to cause a generated GID clash. Using
> Vignesh's test script I could reproduce the problem exactly as
> described. The fix makes the GID unique by including the subid. Now
> the same script runs to normal completion and produces good/expected
> output:
>
> transaction | gid | prepared |
> owner | database
> -------------+------------------+-------------------------------+----------+----------
> 547 | pg_gid_16389_543 | 2021-03-30 10:32:36.87207+11 |
> postgres | postgres
> 555 | pg_gid_16390_543 | 2021-03-30 10:32:48.087771+11 |
> postgres | postgres
> (2 rows)
>
Thanks for the patch with the fix, the fix solves the issue reported.
Regards,
Vignesh