From: | Dominique Devienne <ddevienne(at)gmail(dot)com> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Seq Scan because of stats or because of cast? |
Date: | 2023-03-14 14:56:24 |
Message-ID: | CAFCRh--1GsKA+8=vBM3YFifw9BtQ==OcsndnFmJ1kdP=1Wohuw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Mon, Mar 13, 2023 at 2:53 PM Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
> > PS: libpq uses unsigned int for Oid. So do OIDs go above 2GB in practice?
>
> Yes, eventually.
>
OK, I've added support for native OIDs values (i.e. unsigned int,
sizeof(4)) in my libpq wrapper.
Tested with binary binding and getting of scalar and array values.
But to truly test this is working OK, I'd need OIDs in the range [2^31,
2^32),
while the OIDs in my DB only reach in the 200M range.
So, any way to force the DB to create OIDs in that special range?
Without hosing my DB / Cluster that is... This is not a throw-away DB /
Cluster.
Thanks, --DD
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2023-03-14 17:24:02 | Re: Problems connecting to the server |
Previous Message | Celia McInnis | 2023-03-14 14:19:28 | Re: Uppercase version of ß desired |