I am constructing a large ( by some standards) database where the largest table
threatens to be about 6-10 Gb on a Linux system. I understand that postgresql
splits the tables into manageable chunks & I have no problem with that as a
workround for the 2 GB fs limit
.. My question concerns the
On Tue, 8 Feb 2000, Brian Piatkus wrote:
> I am constructing a large ( by some standards) database where the largest table
> threatens to be about 6-10 Gb on a Linux system. I understand that postgresql
> splits the tables into manageable chunks & I have no problem with that as a
> workround for
Forget my last posting - sorry - I'm being stupid .fs size is, of course 4 Tb
sounds intriguing. although it still use db, but because it
does not need any special db feature (table-locking is
common), it qualifys as "programmatical" solution.
however, not totally understood yet, let's see:
comparing to file locking (e.g. perl's flock)
1) locking is enforced. safer tha
> sounds intriguing. although it still use db, but because it
> does not need any special db feature (table-locking is
> common), it qualifys as "programmatical" solution.
>
> however, not totally understood yet, let's see:
>
> comparing to file locking (e.g. perl's flock)
> 1) locking is enf
