From: | Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com> |
---|---|
To: | Adrian von Bidder <avbidder(at)fortytwo(dot)ch> |
Cc: | pgsql-general(at)postgresql(dot)org |
Subject: | Re: Minimizing disk space |
Date: | 2010-01-06 17:35:22 |
Message-ID: | dcc563d11001060935s32a285d6gfb5e8e01b6f7b187@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On Wed, Jan 6, 2010 at 8:39 AM, Adrian von Bidder <avbidder(at)fortytwo(dot)ch> wrote:
> Howdy!
> With our test dump, the db (after import) is ca. 300M on disk, ca. half in
> WAL files (pg_xlog.) If I could mostly get rid of the WAL (keep it to a
> bare minimum and run pg without fsync, something like that), the remaining
> 160 to 180M would be ok.
>
> Next thing would be: are there tunables (compile time?) to minimize the
> actual size of the rows?
>
> Your input is valued, thanks in advance.
Have you looked at firebird and / or sqllite? They're both far better
suited for this type of application.
From | Date | Subject | |
---|---|---|---|
Next Message | Raymond O'Donnell | 2010-01-06 17:59:31 | Re: How psql source code can be protected? |
Previous Message | Joshua D. Drake | 2010-01-06 17:26:05 | Re: Minimizing disk space |