| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Masahiko Sawada <masahiko(dot)sawada(at)2ndquadrant(dot)com> |
| Cc: | Justin Pryzby <pryzby(at)telsasoft(dot)com>, Mahendra Singh Thalor <mahi6run(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Amit Kapila <akapila(at)postgresql(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: display offset along with block number in vacuum errors |
| Date: | 2020-08-05 11:19:15 |
| Message-ID: | CA+TgmoaPAYnWS1e1UuvDv0rBUSLpBqsmT_kGxuaq63dRFQrwoA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sun, Aug 2, 2020 at 10:43 PM Masahiko Sawada
<masahiko(dot)sawada(at)2ndquadrant(dot)com> wrote:
> I think that since the user who uses this errcontext information is
> likely to know more or less the internal of PostgreSQL I think 0-based
> block number and 1-based offset will not be a problem. However, I
> expected these are documented but couldn't find. If not yet, I think
> it’s a good time to document that.
I agree. That's just how TIDs are.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bharath Rupireddy | 2020-08-05 11:24:37 | Re: Can a background worker exist without shared memory access for EXEC_BACKEND cases? |
| Previous Message | Dmitry Dolgov | 2020-08-05 11:09:38 | Re: LSM tree for Postgres |