From: | markMLl(dot)pgsql-general(at)telemetry(dot)co(dot)uk |
---|---|
To: | pgsql-general(at)PostgreSQL(dot)org |
Subject: | Re: 2 gig file size limit |
Date: | 2001-07-11 12:06:05 |
Message-ID: | 3B4C412D.7C78B564@telemetry.co.uk |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers pgsql-jdbc pgsql-patches |
Ian Willis wrote:
>
> Postgresql transparently breaks the db into 1G chunks.
Yes, but presumably these are still in the directory tree that was
created by initdb, i.e. normally on a single filesystem.
> The main concern is during dumps. A 10G db can't be dumped if the
> filesustem has a 2G limit.
Which is why somebody suggested piping into tar or whatever.
> Linus no longer has a filesystem file size limit ( or at least on
> that you'll hit easily)
I'm not concerned with "easily". Telling one of our customers that we
chose a particular server becuase they won't easily hit limits is a
non-starter.
--
Mark Morgan Lloyd
markMLl .AT. telemetry.co .DOT. uk
[Opinions above are the author's, not those of his employers or
colleagues]
From | Date | Subject | |
---|---|---|---|
Next Message | Graeme Longman | 2001-07-11 12:06:31 | How do system tables relate to other tables in postgresql |
Previous Message | Tim Barnard | 2001-07-11 10:57:29 | Re: vacuum and 24/7 uptime |
From | Date | Subject | |
---|---|---|---|
Next Message | Hannu Krosing | 2001-07-11 12:11:26 | Re: Any tips for this particular performance problem? |
Previous Message | Mike Mascari | 2001-07-11 11:20:22 | Possible feature? |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2001-07-11 12:57:39 | Re: 2 gig file size limit |
Previous Message | Tim Barnard | 2001-07-11 10:57:29 | Re: vacuum and 24/7 uptime |
From | Date | Subject | |
---|---|---|---|
Next Message | Martijn van Oosterhout | 2001-07-11 12:57:39 | Re: 2 gig file size limit |
Previous Message | markMLl.pgsql-general | 2001-07-11 10:00:10 | Re: 2 gig file size limit |