Skip site navigation (1) Skip section navigation (2)

Re: High Disk write and space taken by PostgreSQL

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Ondrej Ivanič <ondrej(dot)ivanic(at)gmail(dot)com>
Cc: J Ramesh Kumar <rameshj1977(at)gmail(dot)com>,pgsql-performance(at)postgresql(dot)org
Subject: Re: High Disk write and space taken by PostgreSQL
Date: 2012-08-16 14:53:21
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-performance
On Thu, Aug 16, 2012 at 03:48:57PM +1000, Ondrej Ivanič wrote:
> Hi,
> On 16 August 2012 15:40, J Ramesh Kumar <rameshj1977(at)gmail(dot)com> wrote:
> > As you said, MySQL with MyISAM is better choice for my app. Because I don't
> > need transaction/backup. May be I'll try with InnoDB and find the disk
> > write/space difference. Is there any similar methods available in postgresql
> > like MyISAM engine ?
> You can try unlogged tables:
> If specified, the table is created as an unlogged table. Data written
> to unlogged tables is not written to the write-ahead log (see Chapter
> 29), which makes them considerably faster than ordinary tables.
> However, they are not crash-safe: an unlogged table is automatically
> truncated after a crash or unclean shutdown. The contents of an
> unlogged table are also not replicated to standby servers. Any indexes
> created on an unlogged table are automatically unlogged as well;
> however, unlogged GiST indexes are currently not supported and cannot
> be created on an unlogged table.

I would set full_page_writes = off too.

  Bruce Momjian  <bruce(at)momjian(dot)us>

  + It's impossible for everything to be true. +

In response to


pgsql-performance by date

Next:From: Bruce MomjianDate: 2012-08-16 14:56:21
Subject: Re: High Disk write and space taken by PostgreSQL
Previous:From: Tom LaneDate: 2012-08-16 06:01:51
Subject: Re: 7k records into Sort node, 4.5m out?

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group