Re: update on TOAST status'

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: update on TOAST status'
Дата
Msg-id 10211.962985831@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: update on TOAST status'  (JanWieck@t-online.de (Jan Wieck))
Ответы Re: update on TOAST status'  (JanWieck@t-online.de (Jan Wieck))
Список pgsql-hackers
JanWieck@t-online.de (Jan Wieck) writes:
>     ... So do we want to  have  indices  storing  plain
>     values allways and limit them in the index-tuple size or not?

I think not: it will be seen as a robustness failure, even (or
especially) if it doesn't happen often.  I can see the bug reports now:
"Hey!  I tried to insert a long value in my field, and it didn't work!
I thought you'd fixed this bug?"

You make good arguments that we shouldn't be too concerned about the
speed of access to toasted index values, and I'm willing to accept
that point of view (at least till we have hard evidence about it).
But when I say "it should be bulletproof" I mean it should *work*,
without imposing arbitrary limits on the user.  Arbitrary limits are
exactly what we are trying to eliminate.
        regards, tom lane


В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: Re: [SQL] Re: [GENERAL] lztext and compression ratios...
Следующее
От: Peter Eisentraut
Дата:
Сообщение: Re: Re: pg_dump and LOs (another proposal)