Re: question about relation_open - Mailing list pgsql-hackers

From Giampaolo Capelli
Subject Re: question about relation_open
Date
Msg-id CAJ=H7uydvT5TH+VYCSgNZN4h78brz_bo6f+U4phBHUq83RpeEA@mail.gmail.com
Whole thread Raw
In response to Re: question about relation_open  (Tom Lane <tgl@sss.pgh.pa.us>)
List pgsql-hackers
It seems the issue was related to some misconfiguration of my postgresql server, 
I've migrated from pg 14 to 17 and now the issue has disappeared.

Also, I replaced relation_open with table_open

Le mar. 14 janv. 2025 à 15:40, Tom Lane <tgl@sss.pgh.pa.us> a écrit :
Giampaolo Capelli <giampow@gmail.com> writes:
> The function relation_open returns a non NULL pointer in my extension, but
> then the last line in the following snippet crashes postgres.

> Relation rel;
> rel = relation_open(relid, AccessShareLock);

> Assert(rel != NULL);
> Assert(rel->rd_rel != NULL);
> Assert(rel->rd_id != NULL);
> elog(INFO, "rel->rd_id not null");
> Oid rd_id = rel->rd_id;

Hmm, I'm a little bit doubting your statement that relation_open
succeeded.  I wonder if maybe you built your extension without asserts
enabled ...

                        regards, tom lane


--
Giampaolo Capelli

pgsql-hackers by date:

Previous
From: Nazir Bilal Yavuz
Date:
Subject: Re: per backend I/O statistics
Next
From: Peter Eisentraut
Date:
Subject: Re: Index AM API cleanup