| From: | Teodor Sigaev <teodor(at)sigaev(dot)ru> |
|---|---|
| To: | Jeff Davis <pgsql(at)j-davis(dot)com> |
| Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Proposal: GiST constraints |
| Date: | 2008-06-10 12:59:21 |
| Message-ID: | 484E7AA9.80003@sigaev.ru |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> This can be solved by my proposal, but I just don't know how it would
> apply to something like GIN, for instance. It could replace the unique
Hmm, your proposal isn't applicable to GIN, because GIN stores a lot of keys for
only one value to be indexed.
> being inserted by other concurrent transactions, and those values can
> be variable in size. What other mechanism do we have to share those
> variable-sized values among several backends?
In theory, any indexed value in index (for GiST, after compression) should fit
into page at least.
--
Teodor Sigaev E-mail: teodor(at)sigaev(dot)ru
WWW: http://www.sigaev.ru/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Zdenek Kotala | 2008-06-10 13:11:50 | Re: RFD: ALTER COLUMN .. SET STORAGE COMPRESSED; |
| Previous Message | Teodor Sigaev | 2008-06-10 12:50:45 | Re: Proposal: GiST constraints |