| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> |
| Cc: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com>, "Andrey M(dot) Borodin" <x4mmm(at)yandex-team(dot)ru>, MBeena Emerson <mbeena(dot)emerson(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de>, Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: recovering from "found xmin ... from before relfrozenxid ..." |
| Date: | 2020-08-11 14:03:29 |
| Message-ID: | CA+TgmobEV99ok7+e4n1aJMt_4vZF6Wh01Tq2=OU2hWcmvOSNtA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Tue, Aug 11, 2020 at 3:39 AM Ashutosh Sharma <ashu(dot)coek88(at)gmail(dot)com> wrote:
> The other two messages for reporting unused items and dead items
> remain the same. Hence, with above change, we would be reporting the
> following 4 messages:
>
> NOTICE: skipping all the tids in block %u for relation "%s" because
> the block number is out of range
>
> NOTICE: skipping tid (%u, %u) for relation "%s" because the item
> number is out of range for this block
>
> NOTICE: skipping tid (%u, %u) for relation "%s" because it is marked dead
>
> NOTICE: skipping tid (%u, %u) for relation "%s" because it is marked unused
>
> Please let me know if you are okay with the above changes or not?
That seems broadly reasonable, but I would suggest phrasing the first
message like this:
skipping block %u for relation "%s" because the block number is out of range
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | vignesh C | 2020-08-11 14:38:11 | Re: Parallel worker hangs while handling errors. |
| Previous Message | Bharath Rupireddy | 2020-08-11 13:20:27 | Inconsistent behavior of smart shutdown handling for queries with and without parallel workers |