Re: remove pg_class.relhaspkey

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Michael Paquier <michael(at)paquier(dot)xyz>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>
Cc: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: remove pg_class.relhaspkey
Date: 2018-03-14 19:36:28
Message-ID: c87ab757-9de6-00fd-6426-74f6903f28fa@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 3/14/18 01:47, Michael Paquier wrote:
>> For the other flags we would probably need to test what impact would it
>> have (e.g. table with no indexes, many indexes on other tables, and
>> something calling get_relation_info a lot). But this patch proposes to
>> remove only relhaspkey.
>
> Yes, you are right here. Peter, would you do that within this commit
> fest or not?

Not terribly interested in those other ones.

> As we are half-way through the commit fest, we could also
> cut the apple in half and just remove relhaspkey for now as that's a
> no-brainer. So I would suggest to just do the latter and consider this
> patch as done.

done

--
Peter Eisentraut http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Dave Page 2018-03-14 21:33:00 Re: Re: Re: [GSOC 18] Performance Farm Project——Initialization Project
Previous Message Pavel Stehule 2018-03-14 19:33:50 Re: SQL/JSON: functions