From: | Philip Warner <pjw(at)rhyme(dot)com(dot)au> |
---|---|
To: | Jan Wieck <JanWieck(at)Yahoo(dot)com>, PostgreSQL HACKERS <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: update on TOAST status' |
Date: | 2000-07-11 12:57:28 |
Message-ID: | 3.0.5.32.20000711225728.02708e50@mail.rhyme.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
At 14:38 11/07/00 +0200, Jan Wieck wrote:
>> Can I suggest that we also put out a warning when defining an index using a
>> field with a (potentially) unlimited size? Indexing a text field will
>> mostly be a bizarre thing to do, but, eg, indexing the first 255 chars of a
>> text field (via substr) might not be.
>
> Marking it BOLD somewhere in the release notes, the CREATE
> INDEX doc and some other places should be enough. Such a
> message at every CREATE INDEX is annoying.
The suggestion was only if the index contained a text, lztext etc field,
but no problem. The way I read your suggestion was that I'd get a real
error when doing an insert if the text was too large.
----------------------------------------------------------------
Philip Warner | __---_____
Albatross Consulting Pty. Ltd. |----/ - \
(A.C.N. 008 659 498) | /(@) ______---_
Tel: (+61) 0500 83 82 81 | _________ \
Fax: (+61) 0500 83 82 82 | ___________ |
Http://www.rhyme.com.au | / \|
| --________--
PGP key available upon request, | /
and from pgp5.ai.mit.edu:11371 |/
From | Date | Subject | |
---|---|---|---|
Next Message | Jan Wieck | 2000-07-11 12:58:38 | Re: [GENERAL] Slashdot discussion |
Previous Message | Jan Wieck | 2000-07-11 12:38:18 | Re: update on TOAST status' |