Thank you everyone for your valuable input! I will have a look at some other
part of PostgreSQL, and maybe find something else to do instead.
Best,
Georgi
---(end of broadcast)---
TIP 6: explain analyze is your friend
Georgi Chulkov <[EMAIL PROTECTED]> writes:
> Here's the reason why I'm looking at raw device storage for large objects
> only
> (as opposed to all tables): with raw device I/O I can control, to an extent,
> spatial locality. So, if I have an application that wants to store N large
> objects (to
Hi,
Georgi Chulkov wrote:
Please allow me to ask then:
1. In your opinion, would the above scenario indeed benefit from a raw-device
interface for large objects?
No, because file systems also try to do what you outline above. They
certainly don't split sequential data up into blocks and dist
@postgresql.org
Subject:Re: [HACKERS] Raw device I/O for large objects
Hi,
> We've heard this idea proposed before, and it's been shot down as a poor
> use of development effort every time. Check the archives for previous
> threads, but the basic argument goes like this
Hi,
> We've heard this idea proposed before, and it's been shot down as a poor
> use of development effort every time. Check the archives for previous
> threads, but the basic argument goes like this: when Oracle et al did
> that twenty years ago, it was a good idea because (1) operating systems
Georgi Chulkov <[EMAIL PROTECTED]> writes:
> I am looking into implementing raw device I/O for large objects into
> PostgreSQL (maybe for all storage, I'm not sure which would be
> easier/better).
We've heard this idea proposed before, and it's been shot down as a poor
use of development effort
On 9/17/07, Georgi Chulkov <[EMAIL PROTECTED]> wrote:
>
> Could someone please point me to the right places to look at, and how/where to
> get started? Would such a development be useful at all? Is anyone working on
> anything related?
>
> Any feedback / information would be highly appreciated!
>
Hello,
I am a graduate student of computer science and I have been looking at
PostgreSQL for my master's thesis work.
I am looking into implementing raw device I/O for large objects into
PostgreSQL (maybe for all storage, I'm not sure which would be
easier/better). I am extremely new to the co
