Re: Updated ALTER TABLE ... SET TABLESPACE patch

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Gavin Sherry <swm(at)linuxworld(dot)com(dot)au>
Cc: Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au>, Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>, pgsql-patches(at)postgresql(dot)org
Subject: Re: Updated ALTER TABLE ... SET TABLESPACE patch
Date: 2004-07-12 02:54:06
Message-ID: 3944.1089600846@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-patches

Gavin Sherry <swm(at)linuxworld(dot)com(dot)au> writes:
> On Mon, 12 Jul 2004, Christopher Kings-Lynne wrote:
>> I vote for taking it out.

> Pull it. I added it intentionally but now I'm questioning my reasoning
> (which was, sequences might be accessed lots, people might want to put
> them somewhere intentionally).

I thought about that, but AFAICS a heavily used sequence would merely
end up as a single hot entry in the shared buffer arena (or at worst,
an often-hit page in kernel buffers). It could not result in a lot of
actual I/O because it's only one page; at most one would expect one
write per checkpoint cycle. So putting it on particularly fast disk
would be a useless exercise.

regards, tom lane

In response to

Browse pgsql-patches by date

  From Date Subject
Next Message Christopher Kings-Lynne 2004-07-12 03:37:53 Re: Updated ALTER TABLE ... SET TABLESPACE patch
Previous Message Tom Lane 2004-07-12 02:36:51 Re: Updated ALTER TABLE ... SET TABLESPACE patch