Re: BUG #18866: Running pg_freespace() on views triggers an Abort

From: Tender Wang <tndrwang(at)gmail(dot)com>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: tharakan(at)gmail(dot)com, pgsql-bugs(at)lists(dot)postgresql(dot)org, Heikki Linnakangas <hlinnaka(at)iki(dot)fi>
Subject: Re: BUG #18866: Running pg_freespace() on views triggers an Abort
Date: 2025-03-26 01:18:41
Message-ID: CAHewXNm8rkn9Vu-WhmMQMJS2hSqztbJO1cRv5-+Rp99+k43aJw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> 于2025年3月26日周三 00:37写道:

> Tender Wang <tndrwang(at)gmail(dot)com> writes:
> > PG Bug reporting form <noreply(at)postgresql(dot)org> 于2025年3月25日周二 22:42写道:
> >> Passing a view to pg_freespace() triggers an Abort on HEAD.
>
> > I think we can remove the Assert in smgropen().
> > Any thoughts?
>
> That seems like a "solution" that will allow other bugs. pg_freespace
> should be fixed to verify RELKIND_HAS_STORAGE() before it tries to
> access said storage.
>

Thanks for the advice. Please see the attached patch.

--
Thanks,
Tender Wang

Attachment Content-Type Size
v2-0001-Don-t-allow-no-storage-relation-to-get-FSM-info.patch text/plain 1.2 KB

In response to

Responses

Browse pgsql-bugs by date

  From Date Subject
Next Message Euler Taveira 2025-03-26 01:55:52 Re: BUG #18866: Running pg_freespace() on views triggers an Abort
Previous Message Wyatt Berlinic 2025-03-25 22:05:55 ltree gist index "incomplete split"