On Tue, Nov 05, 2013 at 10:42:36PM +0800, Patrick Dung wrote:
> I have seen some databases product that allocate small number of large files.
>
> Please correct me if I am wrong:
>
> MySQL with InnoDB
Actually, InnoDB has a file-per-table mode which I tend to prefer. It
means that when I drop a
Em 05/11/2013 12:51, Albe Laurenz escreveu:
Patrick Dung wrote:
I have seen some databases product that allocate small number of large files.
Please correct me if I am wrong:
MSSQL (one file is the data and another file for the transaction log)
MySQL with InnoDB
Oracle
DB2
I don't know enough
Patrick Dung wrote:
> I have seen some databases product that allocate small number of large files.
>
> Please correct me if I am wrong:
>
> MSSQL (one file is the data and another file for the transaction log)
> MySQL with InnoDB
> Oracle
> DB2
I don't know enough about DB2 and MSSQL, but you a
On Monday, November 4, 2013 10:09 PM, Albe Laurenz
wrote:
Patrick Dung wrote:
> As I have seen, some database created or pre-allocate large physical files on
> the file system to as
> the backend of the database tablespace.
>
> For Postgresql, I have observed that it created several file
Patrick Dung wrote:
> As I have seen, some database created or pre-allocate large physical files on
> the file system to as
> the backend of the database tablespace.
>
> For Postgresql, I have observed that it created several files in the base and
> global directory.
>
> It may be by design, wh
As I have seen, some database created or pre-allocate large physical files on
the file system to as the backend of the database tablespace.
For Postgresql, I have observed that it created several files in the base and
global directory.
It may be by design, what is the pros and cons of this beha
