From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | scrappy(at)hub(dot)org (The Hermit Hacker) |
Cc: | reina(at)nsi(dot)edu, pgsql-admin(at)postgreSQL(dot)org |
Subject: | Re: seperate swap drive, was Re: [ADMIN] Speed problem |
Date: | 1998-11-06 04:35:47 |
Message-ID: | 199811060435.XAA01132@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
> On Thu, 5 Nov 1998, G. Anthony Reina wrote:
>
> > Marc,
> >
> >
> > I'm running PostgreSQL v. 6.3.2. No I don't want to disable
> > fsync just in case someone stops a process midstream (which has
> > happened before-- I figure it could screw up the db). So maybe it is
> > those "memory leaks" that you've suggested. I'll try closing and
> > re-connecting to see if there are any differences. However, I would be
> > interested in downloading v. 6.4. Do you know where to get it? (I
> > think it is a beta version but I couldn't find it on the www site).
>
> First off, fsync() only helps if the system itself
> crashes...someone else might want to correct me, but if a process stops
> midstream, it should not affect the db in any way, shape or form...
>
Yes, only OS crashes. Any other crash, fsync has not affect, because
the buffers get written to the disk. Vadim should have that fixed by
6.5, so we wouln't need fsync anymore.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | William Barber | 1998-11-06 11:48:26 | unsubscribe pgsql-SQL |
Previous Message | The Hermit Hacker | 1998-11-06 03:11:01 | Re: [ADMIN] unable to compile postgresql-6.3.2 on alpha-dec-osf4.0 |