Re: Block at a time ...

От: Tom Lane
Тема: Re: Block at a time ...
Дата: ,
Msg-id: 27894.1268836024@sss.pgh.pa.us
(см: обсуждение, исходный текст)
Ответ на: Re: Block at a time ...  (Greg Stark)
Ответы: Re: Block at a time ...  (Dave Crooke)
Список: pgsql-performance

Скрыть дерево обсуждения

Block at a time ...  (Dave Crooke, )
 Re: Block at a time ...  (Alvaro Herrera, )
  Re: Block at a time ...  ("Pierre C", )
   Re: Block at a time ...  (Greg Stark, )
    Re: Block at a time ...  (Tom Lane, )
     Re: Block at a time ...  (Dave Crooke, )
    Re: Block at a time ...  (Craig James, )
     Re: Block at a time ...  (Scott Carey, )
      Re: Block at a time ...  ("Pierre C", )
       Re: Block at a time ...  (Dave Crooke, )
      Re: Block at a time ...  (Greg Stark, )
      Re: Block at a time ...  (Craig James, )
       Re: Block at a time ...  (Scott Carey, )
    Re: Block at a time ...  (Bob Lunney, )

Greg Stark <> writes:
> I think we need posix_fallocate().

The problem with posix_fallocate (other than questionable portability)
is that it doesn't appear to guarantee anything at all about what is in
the space it allocates.  Worst case, we might find valid-looking
Postgres data there (eg, because a block was recycled from some recently
dropped table).  If we have to write something anyway to zero the space,
what's the point?

            regards, tom lane


В списке pgsql-performance по дате сообщения:

От: Alvaro Herrera
Дата:
Сообщение: Re: Building multiple indexes concurrently
От: Greg Smith
Дата:
Сообщение: Re: Building multiple indexes concurrently