[EMAIL PROTECTED] (Nathan Myers) writes: >> Instead of a partial row CRC, we could just as well use some other bit >> of identifying information, say the row OID. ... > Good. But, wouldn't the TID be more specific? Uh, the TID *is* the pointer from index to heap. There's no redundancy that way. > Would this check be simple enough to be safe for 7.1? It'd probably be safe, but adding OIDs to index tuples would force an initdb, which I'd rather avoid at this stage of the cycle. regards, tom lane
- Re: [HACKERS] CRCs Nathan Myers
- Re: [HACKERS] CRCs Tom Lane
- Re: [HACKERS] CRCs Nathan Myers
- Re: [HACKERS] CRCs Daniele Orlandi
- RE: [HACKERS] CRCs Mikheev, Vadim
- RE: [HACKERS] CRCs Mikheev, Vadim
- Re: [HACKERS] CRCs Tom Lane
- Re: [HACKERS] CRCs Nathan Myers
- Re: [HACKERS] CRCs Tom Lane
- Re: [HACKERS] CRCs Nathan Myers
- Re: [HACKERS] CRCs Tom Lane
- Re: [HACKERS] CRCs Horst Herb
- RE: [HACKERS] CRCs Mikheev, Vadim
- RE: [HACKERS] CRCs Mikheev, Vadim