From: | Rajkumar Raghuwanshi <rajkumar(dot)raghuwanshi(at)enterprisedb(dot)com> |
---|---|
To: | Chris Travers <chris(dot)travers(at)adjust(dot)com> |
Cc: | Peter Geoghegan <pg(at)bowt(dot)ie>, Robert Haas <robertmhaas(at)gmail(dot)com>, "pgsql-hackers(at)postgresql(dot)org" <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: recovering from "found xmin ... from before relfrozenxid ..." |
Date: | 2020-08-18 12:18:23 |
Message-ID: | CAKcux6nzpR2+9Lgf7LSNQbHJN7ycZEC5g8moMr6fU7jXOPiJHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Thanks for suggestion Ashutosh, I have done testing around these suggestion
and found no issues. I will continue testing same with updated patch posted
on this thread.
On Fri, Aug 7, 2020 at 12:45 PM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com>
wrote:
> Thanks Rajkumar for testing the patch.
>
> Here are some of the additional test-cases that I would suggest you to
> execute, if possible:
>
> 1) You may try running the test-cases that you have executed so far
> with SR setup and see if the changes are getting reflected on the
> standby.
>
> 2) You may also try running some concurrent test-cases for e.g. try
> running these functions with VACUUM or some other sql commands
> (preferable DML commands) in parallel.
>
> 3) See what happens when you pass some invalid tids (containing
> invalid block or offset number) to these functions. You may also try
> running these functions on the same tuple repeatedly and see the
> behaviour.
>
> ...
>
> --
> With Regards,
> Ashutosh Sharma
> EnterpriseDB:http://www.enterprisedb.com
Thanks & Regards,
Rajkumar Raghuwanshi
From | Date | Subject | |
---|---|---|---|
Next Message | Bernd Helmle | 2020-08-18 12:41:09 | Documentation patch for backup manifests in protocol.sgml |
Previous Message | Ashutosh Bapat | 2020-08-18 12:06:35 | Re: jsonb, collection & postgres_fdw |