| From: | "Mikheev, Vadim" <vmikheev(at)SECTORBASE(dot)COM> |
|---|---|
| To: | "'Alvaro Herrera'" <alvherre(at)atentus(dot)com>, pgsql-general(at)postgresql(dot)org |
| Cc: | vadim4o(at)email(dot)com |
| Subject: | RE: rserv |
| Date: | 2001-05-08 18:11:52 |
| Message-ID: | 3705826352029646A3E91C53F7189E320165E3@sectorbase2.sectorbase.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> I'm currently creating a new field of type bigint, where I store a
> combination of the primary key, that I can assure will be unique --
> until I get lots of entries in the main tables, that is.
>
> What is the "right" approach for this?
"Right" way would be implement support for multi-column keys in Rserv,
so even for tables without natural PK one could add OID to some existent
key to get uniq identifier for all rows in tables. No one had that
ability so far.
You can use OID as key for Rserv. Unfortunately, you probably will have
to create index on table.oid for better replication performance, but
most likely that index will be useful for replication only, not for
queries.
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Fran Fabrizio | 2001-05-08 18:20:45 | Re: select off of a view going slowly |
| Previous Message | Jeff Eckermann | 2001-05-08 17:03:39 | Adding column breaks function with composite type argument |