| From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
|---|---|
| To: | "'Hiroshi Inoue'" <Inoue(at)tpf(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | AW: OID wraparound (was Re: pg_depend) |
| Date: | 2001-07-20 14:45:19 |
| Message-ID: | 11C1E6749A55D411A9670001FA68796336838E@sdexcsrv1.f000.d0188.sd.spardat.at |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> As I mentioned already I'm implementing updatable cursors
> in ODBC and have half done it. If OIDs would be optional
> my trial loses its validity but I would never try another
> implementation.
But how can you do that ? The oid index is only created by
the dba for specific tables, thus your update would do an update
with a where restriction, that is not indexed.
This would be darn slow, no ?
How about instead selecting the primary key and one of the tid's
(I never remember which, was it ctid ?) instead, so you can validate
when a row changed between the select and the update ?
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Lamar Owen | 2001-07-20 15:07:05 | Re: RPM source files should be in CVS (was Re: psql -l) |
| Previous Message | Eduardo Stern | 2001-07-20 14:34:41 | Re: Large queries - again... |