| From: | Andres Freund <andres(at)anarazel(dot)de> |
|---|---|
| To: | John Naylor <jcnaylor(at)gmail(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: automatically assigning catalog toast oids |
| Date: | 2018-12-12 00:44:29 |
| Message-ID: | 20181212004429.u2njrblbgghvp5ws@alap3.anarazel.de |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Hi,
On 2018-12-11 19:33:23 -0500, John Naylor wrote:
> On 12/11/18, Andres Freund <andres(at)anarazel(dot)de> wrote:
> > I've attached a patch implementing that. I'm not particularly in love
> > with FirstGenbkiObjectId as the symbol, but I couldn't think of
> > something more descriptive.
>
> How about FirstAutoAssignedObjectId?
That sounds too general to me. Could just as well be what
FirstNormalObjectId is, or what FirstBootstrapObjectId is. So between
those I do prefer FirstGenbkiObjectId, as that's clearer. Could go for
FirstGenbkiAssignedObjectId too, but that's probably a bit redundant.
Greetings,
Andres Freund
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2018-12-12 00:52:25 | Re: pg_partition_tree crashes for a non-defined relation |
| Previous Message | John Naylor | 2018-12-12 00:33:23 | Re: automatically assigning catalog toast oids |