| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: remove pg_class.relhaspkey |
| Date: | 2018-02-25 03:21:44 |
| Message-ID: | 11891.1519528904@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com> writes:
> pg_class.relhaspkey doesn't seem to be used or useful for anything, so
> can we remove it? See attached patch.
We've discussed that at least twice before, and not pulled the trigger
for fear of breaking client code.
/message-id/flat/CAA-aLv7sszmU%2BFz-xLo6cOiASUiX0mCRwAMF2FB%3D2j-5MKqb%2BA%40mail.gmail.com
/message-id/flat/20140317185255.20724.49675%40wrigleys.postgresql.org
Not sure that the situation has changed any since then ... it still
comes down to whether we want an API break for client code.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Mark Dilger | 2018-02-25 04:26:24 | Re: [HACKERS] PATCH: multivariate histograms and MCV lists |
| Previous Message | Peter Eisentraut | 2018-02-25 02:27:41 | remove pg_class.relhaspkey |