From: | Stephen Frost <sfrost(at)snowman(dot)net> |
---|---|
To: | Benjamin Schaller <benjamin(dot)schaller(at)s2018(dot)tu-chemnitz(dot)de> |
Cc: | pgsql-hackers(at)postgresql(dot)org |
Subject: | Re: Raw device on PostgreSQL |
Date: | 2020-04-28 12:01:30 |
Message-ID: | 20200428120130.GW13712@tamriel.snowman.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Greetings,
* Benjamin Schaller (benjamin(dot)schaller(at)s2018(dot)tu-chemnitz(dot)de) wrote:
> for an university project I'm currently doing some research on PostgreSQL. I
> was wondering if hypothetically it would be possible to implement a raw
> device system to PostgreSQL. I know that the disadvantages would probably be
> higher than the advantages compared to working with the file system. Just
> hypothetically: Would it be possible to change the source code of PostgreSQL
> so a raw device system could be implemented, or would that cause a chain
> reaction so that basically one would have to rewrite almost the entire code,
> because too many elements of PostgreSQL rely on the file system?
yes, it'd be possible, no, you wouldn't have to rewrite all of PG.
Instead, if you want it to be performant at all, you'd have to write
lots of new code to do all the things the filesystem and kernel do for
us today.
Thanks,
Stephen
From | Date | Subject | |
---|---|---|---|
Next Message | Andreas Karlsson | 2020-04-28 12:10:51 | Re: Raw device on PostgreSQL |
Previous Message | Ashutosh Bapat | 2020-04-28 11:46:03 | Re: PostgreSQL CHARACTER VARYING vs CHARACTER VARYING (Length) |