Re: including PID or backend ID in relpath of temp rels

Поиск
Список
Период
Сортировка
От Tom Lane
Тема Re: including PID or backend ID in relpath of temp rels
Дата
Msg-id 20256.1273007830@sss.pgh.pa.us
обсуждение исходный текст
Ответ на Re: including PID or backend ID in relpath of temp rels  (Alvaro Herrera <alvherre@commandprompt.com>)
Ответы Re: including PID or backend ID in relpath of temp rels  (Greg Stark <gsstark@mit.edu>)
Список pgsql-hackers
Alvaro Herrera <alvherre@commandprompt.com> writes:
> I don't very much like the wildcard idea; but I don't think it's
> unreasonable to refuse to provide a file size.  If the owning backend
> has still got part of the table in local buffers, you'll get a
> misleading answer, so perhaps it's best to not give an answer at all.

FWIW, that's not the case, anymore than it is for blocks in shared
buffer cache for regular rels.  smgrextend() results in an observable
extension of the file EOF immediately, whether or not you can see
up-to-date data for those pages.

Now people have often complained about the extra I/O involved in that,
and it'd be nice to have a solution, but it's not clear to me that
fixing it would be harder for temprels than regular rels.
        regards, tom lane


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

Предыдущее
От: Tom Lane
Дата:
Сообщение: Re: including PID or backend ID in relpath of temp rels
Следующее
От: Robert Haas
Дата:
Сообщение: Re: including PID or backend ID in relpath of temp rels