| From: | "Joel Jacobson" <joel(at)compiler(dot)org> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | "Robert Haas" <robertmhaas(at)gmail(dot)com>, "Craig Ringer" <craig(dot)ringer(at)enterprisedb(dot)com>, "Peter Eisentraut" <peter(dot)eisentraut(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Add primary keys to system catalogs |
| Date: | 2021-01-18 20:56:23 |
| Message-ID: | 778cf9a3-f366-4bba-a6e6-ad1e1c580a92@www.fastmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Mon, Jan 18, 2021, at 19:33, Tom Lane wrote:
> On second thought, a catalog is overkill; it'd only be useful if the data
> could change after initdb, which this data surely cannot. The right way
> to expose such info to SQL is with a set-returning function reading a
> constant table in the C code, a la pg_get_keywords(). That way takes a
> whole lot less infrastructure and is just as useful to SQL code.
+1
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2021-01-18 20:58:35 | Re: Narrow the scope of the variable outputstr in logicalrep_write_tuple |
| Previous Message | John Naylor | 2021-01-18 20:54:20 | Re: truncating timestamps on arbitrary intervals |