Re: Why don't we have a small reserved OID range for patch revisions? - Mailing list pgsql-hackers

From John Naylor
Subject Re: Why don't we have a small reserved OID range for patch revisions?
Date
Msg-id CACPNZCsxOVsg6=U5pz3xNKX8G=Q-6AT=i2Fp=37KwCL_FdxT_Q@mail.gmail.com
Whole thread Raw
In response to Re: Why don't we have a small reserved OID range for patch revisions?  (John Naylor <john.naylor@2ndquadrant.com>)
List pgsql-hackers
I wrote:

> Along those lines, here's a draft patch to do just that. It handles
> array type oids as well. Run it like this:
>
> perl  reformat_dat_file.pl  --map-from 9000  --map-to 2000  *.dat
>
> There is some attempt at documentation. So far it doesn't map by
> default, but that could be changed if we agreed on the convention of
> 9000 or whatever.

In case we don't want to lose track of this, I added it to the March
commitfest with a target of v13. (I didn't see a way to  add it to the
July commitfest)

-- 
John Naylor                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: John Naylor
Date:
Subject: Re: WIP: Avoid creation of the free space map for small tables
Next
From: Surafel Temesgen
Date:
Subject: Re: Add --include-table-data-where option to pg_dump, to export onlya subset of table data