| From: | "Roderick A(dot) Anderson" <raanders(at)acm(dot)org> |
|---|---|
| To: | "Nigel J(dot) Andrews" <nandrews(at)investsystems(dot)co(dot)uk> |
| Cc: | Oleg Bartunov <oleg(at)sai(dot)msu(dot)su>, <pgsql-general(at)postgresql(dot)org>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: [HACKERS] postgresql performance tuning document ? |
| Date: | 2002-08-08 22:32:58 |
| Message-ID: | Pine.LNX.4.33.0208081529210.15453-100000@main.cyber-office.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general pgsql-hackers |
On Thu, 8 Aug 2002, Nigel J. Andrews wrote:
> > I see files truncated at 1Gb on my Linux server:
> >
> > -rw------- 1 postgres users 855490560 Aug 6 20:53 795261707.2
> > -rw------- 1 postgres users 943259648 Aug 8 23:34 823049708
> > -rw------- 1 postgres users 1073741824 Aug 6 20:53 795261707.1
> > -rw------- 1 postgres users 1073741824 Aug 6 20:53 795261707
> >
> > I'm wondering if postgresql doesn't have LARGE_FILES support ?
I'm a user not a hacker but I seem to remember a discussion on this
before. Part of the design was to break the files at approx. 1GByte
partly or wholly to avoid any OS file size limitation.
Rod
--
"Open Source Software - Sometimes you get more than you paid for..."
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeff Eckermann | 2002-08-08 23:06:04 | UNIQUE constraint matching given keys for referenced table "employee" not found |
| Previous Message | Oleg Bartunov | 2002-08-08 22:11:06 | postgresql performance tuning document ? |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Joe Conway | 2002-08-08 22:48:41 | Re: stand-alone composite types patch (was [HACKERS] Proposal: |
| Previous Message | Oleg Bartunov | 2002-08-08 22:11:06 | postgresql performance tuning document ? |