Re: odd postgresql performance (excessive lseek)

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Jon Nelson <jnelson+pgsql(at)jamponi(dot)net>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: odd postgresql performance (excessive lseek)
Date: 2010-10-19 14:36:09
Message-ID: 10133.1287498969@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Jon Nelson <jnelson+pgsql(at)jamponi(dot)net> writes:
> This is another situation where using pread would have saved a lot of
> time and sped things up a bit, but failing that, keeping track of the
> file position ourselves and only lseek'ing when necessary would also
> help.

No, it wouldn't; you don't have the slightest idea what's going on
there. Those lseeks are for the purpose of detecting the current EOF
location, ie, finding out whether some other backend has extended the
file recently. We could get rid of them, but only at the cost of
putting in some other communication mechanism instead.

regards, tom lane

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Kevin Grittner 2010-10-19 15:16:31 Re: HashJoin order, hash the large or small table? Postgres likes to hash the big one, why?
Previous Message Tom Lane 2010-10-19 14:25:34 Re: Help with duration of statement: EXECUTE <unnamed> [PREPARE: COMMIT]