| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-hackers(at)lists(dot)postgresql(dot)org, Rushabh Lathia <rushabh(dot)lathia(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)enterprisedb(dot)com> |
| Subject: | Re: Replacing pg_depend PIN entries with a fixed range check |
| Date: | 2021-05-26 15:11:26 |
| Message-ID: | CA+TgmobXixznpObPhbiePX9VL5GhN3LaHSXsLQ0oJvK1sC319Q@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, May 12, 2021 at 6:21 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> Here's a v2 that does things that way (and is rebased up to HEAD).
> I did some more documentation cleanup, too.
The first hunk of the patch seems to back away from the idea that the
cutoff is 13000, but the second half of the patch says 13000 still
matters. Not sure I understand what's going on there exactly.
I suggest deleting the words "An additional thing that is useful to
know is that" because the rest of the sentence is fine without it.
I'm sort of wondering what we think the long term plan ought to be.
Are there some categories of things we should be looking to move out
of the reserved OID space to keep it from filling up? Can we
realistically think of moving the 16384 boundary?
--
Robert Haas
EDB: http://www.enterprisedb.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Konstantin Knizhnik | 2021-05-26 15:11:52 | Re: Add ZSON extension to /contrib/ |
| Previous Message | Ibrar Ahmed | 2021-05-26 14:52:17 | Re: Next Commitfest Manager. |