| From: | Peter Eisentraut <peter(at)eisentraut(dot)org> |
|---|---|
| To: | Ashutosh Bapat <ashutosh(dot)bapat(dot)oss(at)gmail(dot)com>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: Type of property graph |
| Date: | 2026-05-04 13:52:05 |
| Message-ID: | 2da510ef-c51d-4777-831f-5a62080c159d@eisentraut.org |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 30.04.26 14:29, Ashutosh Bapat wrote:
> We create a pg_type entry for a property graph, but it's not used
> anywhere and it doesn't make sense to create a type for a property
> graph which doesn't hold any rows or can be associated with a specific
> result type. We have other pg_class entries which do not have a type
> associated with them. I think we should do the same for property graph
> as well. Here's patch with that change. It doesn't show any failure in
> make check as well.
Agreed, committed. I included a catversion bump.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2026-05-04 13:56:28 | Re: PoC: VALGRIND_MAKE_MEM_NOACCESS for dynamic shared memory |
| Previous Message | Tomas Vondra | 2026-05-04 13:51:20 | Re: EXPLAIN: showing ReadStream / prefetch stats |