| From: | Joshua Drake <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Lucas <lucas75(at)gmail(dot)com> |
| Cc: | pgsql-general(at)lists(dot)postgresql(dot)org |
| Subject: | Re: Cluster OID Limit |
| Date: | 2022-06-09 17:22:37 |
| Message-ID: | CAJvJg-TNNdPUfqKCMBFcMGwTo9BDjcENtAbci2dB6xc72Lbp2g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
Lucas,
If you run out of OIDs you are doing something wrong. We haven't supported
user space OIDs in a lot of releases. Which release are you using?
JD
On Thu, Jun 9, 2022 at 2:11 AM Lucas <lucas75(at)gmail(dot)com> wrote:
> Hello,
>
> In the company I work for, some clusters reached the OID limit (2^32) and
> we had to reinstall the cluster.
>
> I was wondering if there is any discussion on:
> * "compress" the OID space
> * "warp around" the OID space
> * segment a OID range for temporary tables with "wrap around"
>
> --
> Lucas
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joshua Drake | 2022-06-09 17:23:16 | Re: Sharing DSA pointer between parallel workers after they've been created |
| Previous Message | SERHAD ERDEM | 2022-06-09 15:08:26 | Re: Cluster OID Limit |