hello,

thanks for the logical answer. it is true that there is a very big
difference between open source and commercial DB. but I'm grateful to be
able to use postgresql which is quite reliable.

thank you
Yours faithfully

yudianto

<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Virus-free.
www.avg.com
<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

On Mon, Jan 31, 2022 at 12:10 PM Laurenz Albe <laurenz.a...@cybertec.at>
wrote:

> On Sun, 2022-01-30 at 05:15 +0700, Yudianto Prasetyo wrote:
> > I want to ask why postgresql doesn't create a datafile like it has
> oracle?
> >
> > I'm confused when I have 2 HDD. HDD 1 is used to install the OS and
> postgresql database.
> > when HDD 1 is full. how to increase the capacity of postgresql database
> with HDD 2 (without RAID system)?
> >
> > is there any other way like oracle DB's "add datafile" which can be used
> to add capacity to another HDD?
>
> The difference between Oracle and PostgreSQL here is that Oracle
> implemented its
> own file system and volume manager, while PostgreSQL uses the facilities
> provided
> by the operating system.
>
> The correspondence is not perfect, but you can compare an Oracle
> tablespace to
> a logical volume with a file system and a datafile to a physical volume.
>
> So to get the same thing in PostgreSQL, you have to interact with the
> operating
> system: add a new physical volume to the logical volume where your database
> resides and extend the file system.
>
> To answer the question "why", here are two points:
>
> - PostgreSQL does not have the (wo)manpower to re-invent the wheel on
> everything,
>   so we tend to use existing facilities
>
> - Oracle was developed earlier, and one can argue that in those days file
> systems
>   were not so great, so there was more need to write your own
>
> Yours,
> Laurenz Albe
> --
> Cybertec | https://www.cybertec-postgresql.com
>
>

Reply via email to