Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread Merlin Moncure
On Wed, Aug 15, 2012 at 11:30 PM, J Ramesh Kumar wrote: > > Hi David Barton, > > Please find the information below. > >> Are you able to provide a table schema? > > > There are 109 different types of table. I am maintaining some tables are > daily tables and some tables are ID based. So totally we

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread Bruce Momjian
On Thu, Aug 16, 2012 at 06:07:26PM +0200, anara...@anarazel.de wrote: > > > Bruce Momjian schrieb: > > >On Thu, Aug 16, 2012 at 03:48:57PM +1000, Ondrej Ivanič wrote: > >> Hi, > >> > >> On 16 August 2012 15:40, J Ramesh Kumar > >wrote: > >> > As you said, MySQL with MyISAM is better choice fo

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread anara...@anarazel.de
Bruce Momjian schrieb: >On Thu, Aug 16, 2012 at 03:48:57PM +1000, Ondrej Ivanič wrote: >> Hi, >> >> On 16 August 2012 15:40, J Ramesh Kumar >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 f

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread Scott Marlowe
On Wed, Aug 15, 2012 at 11:40 PM, J Ramesh Kumar wrote: > Dear Scott Marlowe, > > Thanks for the details. > > As you said, MySQL with MyISAM is better choice for my app. Because I don't > need transaction/backup. That's not exactly what I said. Remember that if you need to run complex queries po

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread Bruce Momjian
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 wrote: > > > As you said, MySQL with MyISAM is better choice for my app. Because I > > > don't > > > need transa

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-16 Thread Bruce Momjian
On Thu, Aug 16, 2012 at 03:48:57PM +1000, Ondrej Ivanič wrote: > Hi, > > On 16 August 2012 15:40, J Ramesh Kumar 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 differ

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread Claudio Freire
On Thu, Aug 16, 2012 at 2:40 AM, J Ramesh Kumar wrote: Ahhh but updates are the basically delete / inserts in disguise, so if there's enough, then yes, vacuum full would make a difference. > > The table which get update has very less data ie, only has 900 rows. Out of > 10500 tables, onl

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread Ondrej Ivanič
Hi, On 16 August 2012 15:40, J Ramesh Kumar 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 en

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread Claudio Freire
On Thu, Aug 16, 2012 at 1:30 AM, J Ramesh Kumar wrote: > # To avoid freqent autovacuum > autovacuum_freeze_max_age = 20 > vacuum_freeze_min_age = 1000 > vacuum_freeze_table_age = 15000 > In general, I'm no expert, but I've heard, increasing freeze_max_age isn't wise. It's there to

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread J Ramesh Kumar
Dear Scott Marlowe, Thanks for the details. 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 ? >>> Ahh

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread Scott Marlowe
Please use plain text on the list, some folks don't have mail readers that can handle html easily. On Wed, Aug 15, 2012 at 10:30 PM, J Ramesh Kumar wrote: > > Hi David Barton, > > Please find the information below. > >> Are you able to provide a table schema? > > > There are 109 different types o

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread J Ramesh Kumar
Hi David Barton, Please find the information below. Are you able to provide a table schema? There are 109 different types of table. I am maintaining some tables are daily tables and some tables are ID based. So totally we have created around 350 tables and dropped around 350 tables. I will drop

Re: [PERFORM] High Disk write and space taken by PostgreSQL

2012-08-15 Thread David Barton
Hi Ramesh, Are you able to provide a table schema? Were you using MyISAM or InnoDB on MySQL? If you back up the database & restore clean, what is the size comparison of the database filed on the restored copy to the existing one? It may be full of empty tuples. Is there any period where y