Re: Caching number of blocks in relation to avoi lseek.

From: Denis Perchine <dyp(at)perchine(dot)com>
To: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Caching number of blocks in relation to avoi lseek.
Date: 2000-06-12 18:11:39
Message-ID: 00061301132305.07937@dyp
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

> > Question: is this field properly updated? Could it be used instead of RelationGetNumberOfBlocks
> > which calls lseek.
>
> Probably should be kept up-to-date. Currently only vacuum sets it. It
> would have to be kept up-to-date for every INSERT/UPDATE that adds a block.

If we can acomplish this it will be quite big speed improvement. I saw lots of such calls
and strace show lots of lseek(,,END) calls. I would do this, but I do not know the code so
well to be sure I will walk through all places.

--
Sincerely Yours,
Denis Perchine

----------------------------------
E-Mail: dyp(at)perchine(dot)com
HomePage: http://www.perchine.com/dyp/
FidoNet: 2:5000/120.5
----------------------------------

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message valter m 2000-06-12 18:31:03 full text indexing & search
Previous Message Bruce Momjian 2000-06-12 18:05:45 Re: Caching number of blocks in relation to avoi lseek.

Browse pgsql-patches by date

  From Date Subject
Next Message Denis Perchine 2000-06-12 18:13:42 Re: Patch for better large objects support
Previous Message Bruce Momjian 2000-06-12 18:05:45 Re: Caching number of blocks in relation to avoi lseek.