pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  

help / color / mirror / Atom feed
From: Bruce Momjian <bruce@momjian.us>
To: Ondrej Ivanič <ondrej.ivanic@gmail.com>
Cc: J Ramesh Kumar <rameshj1977@gmail.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: High Disk write and space taken by PostgreSQL
Date: Thu, 16 Aug 2012 10:53:21 -0400
Message-ID: <20120816145321.GA8359@momjian.us> (raw)
In-Reply-To: <CAM6mieJqV0=KX2MuTXz+jr8_RCpzmNn0w6A9E5XsAcxKsSP5SQ@mail.gmail.com>
References: <CA+-36iFtmVsuvrXbahBX=29Sn-9XsaZpWHQfg9dmOf3SEkJcug@mail.gmail.com>
	<502C6AD5.4070407@oneit.com.au>
	<CA+-36iGrckXc3bvpJJ0AECjFeaoDpX892jyyJ2Hk-K=bHwDSvA@mail.gmail.com>
	<CAOR=d=1H1-p7SovzTh0y0NWvo9a9Xf7uvH8iGPJA6NZy2oJv8g@mail.gmail.com>
	<CA+-36iFvm6fYrBYOxjPAhGkxN34P01vy7MqiCz0inZ1dcnUpEA@mail.gmail.com>
	<CAM6mieJqV0=KX2MuTXz+jr8_RCpzmNn0w6A9E5XsAcxKsSP5SQ@mail.gmail.com>

On Thu, Aug 16, 2012 at 03:48:57PM +1000, Ondrej Ivanič wrote:
> Hi,
> 
> On 16 August 2012 15:40, J Ramesh Kumar <rameshj1977@gmail.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.

-- 
  Bruce Momjian  <bruce@momjian.us>        http://momjian.us
  EnterpriseDB                             http://enterprisedb.com

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




view thread (14+ messages)  latest in thread

Message-ID: <20120816145321.GA8359@momjian.us>
Permalink:  ../20120816145321.GA8359@momjian.us/
Also on:    postgresql.org/message-id/20120816145321.GA8359@momjian.us

 · 

reply
Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: bruce@momjian.us, ondrej.ivanic@gmail.com, rameshj1977@gmail.com
  Subject: Re: High Disk write and space taken by PostgreSQL
  In-Reply-To: <20120816145321.GA8359@momjian.us>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox