| From: | John Naylor <jcnaylor(at)gmail(dot)com> |
|---|---|
| To: | Andres Freund <andres(at)anarazel(dot)de> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: [RFC] Removing "magic" oids |
| Date: | 2018-11-15 10:25:21 |
| Message-ID: | CAJVSVGVepnvnYN2TRufCa+dZ-JhVKGo77rtgO2frz1tj+wriHQ@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 11/15/18, Andres Freund <andres(at)anarazel(dot)de> wrote:
> I've now revised this slightly. genbki.pl now computes the maximum oid
> explicitly assigned in .dat files, and assignes oids to all 'oid'
> columns without a value. It does so starting directly at the maximum
> value. I personally don't see need to have implicit .bki oids be in a
> different range, and having them assigned more densely is good for some
> things (e.g. the fmgr builtins table, even though we currently assign
> all proc oids manually).
I don't see an advantage to having a different range, but maybe it
should error out if $maxoid reaches FirstBootstrapObjectId.
This patch breaks reformat_dat_file.pl. I've attached a fix, which
also de-lists oid as a special key within the *.dat files. It might be
good to put off reformatting until feature freeze, so as not to break
others' patches.
-John Naylor
| Attachment | Content-Type | Size |
|---|---|---|
| fix-reformat-dat-files.patch | text/x-patch | 935 bytes |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2018-11-15 10:36:17 | Re: [HACKERS] Transactions involving multiple postgres foreign servers, take 2 |
| Previous Message | Ronan Dunklau | 2018-11-15 10:23:24 | ALTER INDEX ... ALTER COLUMN not present in dump |