| From: | Thomas Munro <thomas(dot)munro(at)gmail(dot)com> |
|---|---|
| To: | Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> |
| Cc: | Andres Freund <andres(at)anarazel(dot)de>, Robert Haas <robertmhaas(at)gmail(dot)com>, Michael Harris <harmic(at)gmail(dot)com>, Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: FileFallocate misbehaving on XFS |
| Date: | 2024-12-14 09:26:37 |
| Message-ID: | CA+hUKGK5QdKqzuoe5-iYH297PW4w4K51K-SkBHC2w3fxf21NnA@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Sat, Dec 14, 2024 at 9:29 PM Alvaro Herrera <alvherre(at)alvh(dot)no-ip(dot)org> wrote:
> On 2024-Dec-11, Andres Freund wrote:
> > One thing that I think we should definitely do is to include more detail in
> > the error message. mdzeroextend()'s error messages don't include how many
> > blocks the relation was to be extended by. Neither mdextend() nor
> > mdzeroextend() include the offset at which the extension failed.
>
> I proposed a patch at
> https://postgr.es/m/202409110955.6njbwzm4ocus@alvherre.pgsql
If adding more logging, I wonder why FileAccess()'s "re-open failed"
case is not considered newsworthy. I've suspected it as a candidate
source of an unexplained and possibly misattributed error in other
cases. I'm not saying it's at all likely in this case, but it seems
like just the sort of rare unexpected failure that we'd want to know
more about when trying to solve mysteries.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Sergei Kornilov | 2024-12-14 09:39:23 | Re: Track the amount of time waiting due to cost_delay |
| Previous Message | Thomas Munro | 2024-12-14 08:58:28 | Re: checkpointer: PANIC: could not fsync file: No such file or directory |