From: | elein <elein(at)norcov(dot)com> |
---|---|
To: | "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com> |
Cc: | <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: OID order = INSERT order? |
Date: | 2002-09-23 20:59:49 |
Message-ID: | 200209232059.g8NKxZI5299618@pimout2-ext.prodigy.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
In 7.3b1, the oids of a row do not change on update
according to my experiment. I had thought they did.
Is this new with 7.3?
elein
elein(at)norcov(dot)com
On Monday 16 September 2002 08:43, scott.marlowe wrote:
> On 13 Sep 2002, Justin Hawkins wrote:
> > Hi folks,
> >
> > I am converting a legacy (DBM file backend) app to SQL. The current
> > storage scheme utlizes ordered list values on objects. To emulate this
> > I'm just doing multiple INSERTs on a table.
> >
> > I need to make sure they will come back out in the same order, every
> > time though.
> >
> > When I fetch values back from the table, if I 'ORDER BY oid', will I
> > always get them back in the same order I put them in?
>
> If you update a row, it will then have a different OID since postgresql
> uses MVCC.
>
> do it the right way, make a sequence and attach it to the table.
>
>
> ---------------------------(end of broadcast)---------------------------
> TIP 4: Don't 'kill -9' the postmaster
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-09-23 21:23:17 | Re: bug(?) : order by function limit x |
Previous Message | Tom Lane | 2002-09-23 20:55:48 | Re: [GENERAL] CURRENT_TIMESTAMP |