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:56:21
Message-ID: 20120816145621.GB8359@momjian.us (view raw or flat)
Thread:
Lists: pgsql-performance
On Thu, Aug 16, 2012 at 10:53:21AM -0400, Bruce Momjian wrote:
> 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:
> > http://www.postgresql.org/docs/9.1/static/sql-createtable.html
> > 
> > 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.

Better yet, read our documentation about non-durable settting:

	http://www.postgresql.org/docs/9.1/static/non-durability.html

-- 
  Bruce Momjian  <bruce(at)momjian(dot)us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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


In response to

pgsql-performance by date

Next:From: Doug HunleyDate: 2012-08-16 15:25:48
Subject: Re: cluster on conditional index?
Previous:From: Bruce MomjianDate: 2012-08-16 14:53:21
Subject: Re: High Disk write and space taken by PostgreSQL

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