Skip site navigation (1) Skip section navigation (2)

Re: OIDS > INT_MAX displayed wrapped around

From: Kris Jurka <books(at)ejurka(dot)com>
To: Guillaume Lelarge <guillaume(at)lelarge(dot)info>
Cc: pgadmin-hackers(at)postgresql(dot)org
Subject: Re: OIDS > INT_MAX displayed wrapped around
Date: 2007-07-31 08:24:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgadmin-hackers

On Tue, 31 Jul 2007, Guillaume Lelarge wrote:

> I don't know how I can build such a test case. My generate_series to
> build a billion inserts just failed with a "write failed" message...
> Here is the patch. It compiles and works on my laptop but I don't know
> if it really fixes the issue. If someone with a big enough database can
> apply the patch and compile pgAdmin with it, I would be really happy to
> know about the result.

I actually have a tiny database that I was testing the JDBC driver's large 
oid handling with and happened across this problem.  You can use 
pg_resetxlog's -o option to set the next oid to any value of your 
choosing.  Or you can wait for beta three and I'll test again.

Kris Jurka

In response to

pgadmin-hackers by date

Next:From: Guillaume LelargeDate: 2007-07-31 08:35:53
Subject: Enabling SQL text field in the SQL tab of object dialog
Previous:From: Guillaume LelargeDate: 2007-07-31 08:15:00
Subject: Re: OIDS > INT_MAX displayed wrapped around

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group