From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | hlee(at)pyxsys(dot)net |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Question about porting the PostgreSQL |
Date: | 2001-07-25 07:01:30 |
Message-ID: | 20333.996044490@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Hsin Lee" <hlee(at)pyxsys(dot)net> writes:
> We would like to get your feedback about this aproach - are we on the
> right track or is it a waste of time?
Impossible to tell, since you haven't said word one about what this
box is or what it can do. If it were plain storage hardware, why do
you need to muck with the innards of Postgres at all? Just use it
as disk. If it's not plain storage, you'll need to be a lot more
specific about what you expect the box to do. If there's lots of
processing power in the box, why don't you just run *all* of Postgres
inside the box? (Running any part of PG on Win2K is not my idea
of the correct solution in any case ;-).)
FWIW, I find it very hard to visualize a case where I'd think that
replacing heapam is the right approach. Replacing the storage
manager could be the right approach for certain situations, but
replacing heapam means replacing a lot of extremely critical
(read breakable) code for no obvious reason.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Turbo Fredriksson | 2001-07-25 09:59:21 | plpgsql: Checking status on a 'INSERT INTO ...' |
Previous Message | Tatsuo Ishii | 2001-07-25 01:14:54 | RE: Thai data import into PostgreSQL |