Thank you Tom for your concise response. Your explanation is very helpfull.
We were aware of the wraparound issues, but this has worked so well for us
that we haven't explored changing it yet. Having a unique identifier per row
is most usefull in our situation and we didn't think we were anyw
Chris Kratz <[EMAIL PROTECTED]> writes:
> We aren't sure at this point if the problem we are having has to do with the
> fact that we drop and reload the test db quite often and so we are running
> into OID wraparound, or if it has to do with the fact that we recently went
> to 8.1 on this test
Hello all,
We have a live server running on PG 8.0.3 which we backup on a regular bases
by doing a pg_dumpall --oids. We have a test server currently running 8.1.1
where we reload that dumpall using psql.
Now we have a history tracking system in the db which via triggers and rules
keeps track
Many thanks to all who have responded. I hope to be as helpful to the list
someday as each of you have been. Thanks...
On Thursday 11 November 2004 10:04 am, Terry Lee Tucker saith:
> Greetings,
>
> Here is a simple question:
>
> Is it ok to put a unique index on the oid for my tables? We are in
At 03:34 PM 11/11/04, Geoffrey wrote:
Bruno Wolff III wrote:
On Thu, Nov 11, 2004 at 10:04:30 -0500, Terry Lee Tucker
<[EMAIL PROTECTED]> wrote:
Greetings,
Here is a simple question:
Is it ok to put a unique index on the oid for my tables? We are in
the process
Yes, but you may occasionally have in
On Thu, Nov 11, 2004 at 15:34:14 -0500,
Geoffrey <[EMAIL PROTECTED]> wrote:
>
> "Whenever an application makes use of OIDs to identify specific rows of
> a table, it is recommended to create a unique constraint on the oid
> column of that table, to ensure that OIDs in the table will indeed
>
On Thu, Nov 11, 2004 at 03:34:14PM -0500, Geoffrey wrote:
> So this prompts a question regarding the documentation. I'm assuming
> that I can address the wrap-around issue based on the following found
> under "Notes" section of the "Create Table" document:
>
> "Whenever an application makes use
Bruno Wolff III wrote:
On Thu, Nov 11, 2004 at 10:04:30 -0500, Terry Lee Tucker
<[EMAIL PROTECTED]> wrote:
Greetings,
Here is a simple question:
Is it ok to put a unique index on the oid for my tables? We are in
the process
Yes, but you may occasionally have insert failures if the oid wraps
around
Terry Lee Tucker wrote:
Greetings,
Here is a simple question:
Is it ok to put a unique index on the oid for my tables? We are in the process
of moving from Progress Software to PostgreSQL. In the Progress world, you
can always uniquely, and quickly find a record by using their version of oid,
wh
On Thu, Nov 11, 2004 at 10:04:30 -0500,
Terry Lee Tucker <[EMAIL PROTECTED]> wrote:
> Greetings,
>
> Here is a simple question:
>
> Is it ok to put a unique index on the oid for my tables? We are in the
> process
Yes, but you may occasionally have insert failures if the oid wraps around
and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thursday 11 November 2004 07:04 am, Terry Lee Tucker wrote:
> Greetings,
>
> Here is a simple question:
>
> Is it ok to put a unique index on the oid for my tables? We are in the
> process of moving from Progress Software to PostgreSQL. In the Progr
On Thu, 11 Nov 2004, Terry Lee Tucker wrote:
> Is it ok to put a unique index on the oid for my tables? We are in the process
> of moving from Progress Software to PostgreSQL. In the Progress world, you
> can always uniquely, and quickly find a record by using their version of oid,
> which is reci
Greetings,
Here is a simple question:
Is it ok to put a unique index on the oid for my tables? We are in the process
of moving from Progress Software to PostgreSQL. In the Progress world, you
can always uniquely, and quickly find a record by using their version of oid,
which is recid. I remem
Chris Sutton wrote:
>
> I would like to use the oid as a unique key for a table but in creating
> a test table and playing around with inserts, things don't seem to be
> working as I thought they would.
>
> Where am I going wrong?
There is a hidden column named 'oid'. Try "select oid, desc fr
I would like to use the oid as a unique key for a table but in creating
a test table and playing around with inserts, things don't seem to be
working as I thought they would.
create table test (
key oid,
desc varchar(30));
Then I do an insert
insert into test (desc) values ('inf
15 matches
Mail list logo
