> Coming late into the discussion, there is one more note I'd add to this
> - if you're on windows and want to be extra secure, also set
> wal_sync_method=fsync_writethrough. This will get it through most (I
> would say all if I was sure, but I'm not) IDE disks that lie about write
> completion.
M
> 1. Windows XP
> 2. QUANTUM FIREBALLP LM20.5 (IDE drive)
> 3. Write caching is off in XP device manager
> 4. fsync is ON in Postgres 8
Coming late into the discussion, there is one more note I'd add to this
- if you're on windows and want to be extra secure, also set
wal_sync_method=fsync_writet
The transistor has existed in homes now for 30 years. That means new
homes should be built to withstand direct lightning strikes without
damage. Such earthing is not difficult. But it requires the builder
to plan for the lightning protection 'system' before the footing are
poured. It is an ol
Destructive surges seek earth ground. Do you think a protector is
going to stop what 3 miles of non-conductive sky could not? And yet
that is exactly what some protectors manufacturers hope you will
assume.
Effective protectors don't stop, block, or absorb typically
destructive transients.
One of the many problems with FAT32 was that files on the drive can
be deleted if power is lost. This is why FAT was obsoleted by HPFS
which in turn was obsoleted by NTFS.
Power loss should not cause data loss which is why we stopped using
FAT even before Windows 95 was released.
Program t
huh never heard of that - I'll hold out testing it for now but thats
good info. (how does it know which partition - if there's 2?)
Troy H
---(end of broadcast)---
TIP 4: Have you searched our list archives?
http://archives.postgresq
I have read it before - it's a _fantastic_ resource, and I will
probably make every junior tech I ever hire read it too.
On 10/28/05, Bruce Momjian wrote:
> Alex Turner wrote:
> > Of course not counting the Western Digital Raptor SATA drive, which
> > are priced more like SCSI drives also, and ha
Alex Turner wrote:
> Of course not counting the Western Digital Raptor SATA drive, which
> are priced more like SCSI drives also, and have many of the features
> of a SCSI drive including NCQ
>
Well, the PDF talks about several aspects of server drives, including
concurrency, performance, and rel
Of course not counting the Western Digital Raptor SATA drive, which
are priced more like SCSI drives also, and have many of the features
of a SCSI drive including NCQ
Alex
On 10/28/05, Bruce Momjian wrote:
> Andrus wrote:
> > >> QUANTUM FIREPALLP LM20.5 is a widely used ATA IDE drive.
> > >>
> >
Andrus wrote:
> >> QUANTUM FIREPALLP LM20.5 is a widely used ATA IDE drive.
> >>
> >> Where do find information does it implement write caching properly or not
> >> ?
> >
> > I don't think the manufacturers bother to make this sort of information
> > available.
> >
> >> Is there IDE drive compati
>> QUANTUM FIREPALLP LM20.5 is a widely used ATA IDE drive.
>>
>> Where do find information does it implement write caching properly or not
>> ?
>
> I don't think the manufacturers bother to make this sort of information
> available.
>
>> Is there IDE drive compatibility list for Postgres ?
>
> N
w_tom wrote:
Series mode protector will ignore or avoid THE one and essential
component of an effective protection system - single point earth
ground.
Indeed. And yes, a high end data center should survive
a lightning strike (as well as hospital's power systems, etc).
Here's a nice articl
On Thu, 2005-10-27 at 15:14, Keith C. Perry wrote:
> Actually, because I lost several thousands of dollars or equipement a couple
> of
> years ago, I recommended these "brickwall" products to a company.
>
> http://brickwall.com/index.htm
>
> We actually never deployed these units (grounding the
Actually, because I lost several thousands of dollars or equipement a couple of
years ago, I recommended these "brickwall" products to a company.
http://brickwall.com/index.htm
We actually never deployed these units (grounding the communications lines ended
up being a much cheaper solution) but I
Andrus wrote:
QUANTUM FIREPALLP LM20.5 is a widely used ATA IDE drive.
Where do find information does it implement write caching properly or not ?
I don't think the manufacturers bother to make this sort of information
available.
Is there IDE drive compatibility list for Postgres ?
No -
On 27 Oct 2005, at 16:07, Tom Lane wrote:
Alex Stapleton <[EMAIL PROTECTED]> writes:
The system RAM won't usually be supported by any batteries though, so
it will go crazy, copy corrupt data to the DIMMs on the RAID
controller, which then will refuse to write it to the disk until the
power co
Alex Stapleton <[EMAIL PROTECTED]> writes:
> The system RAM won't usually be supported by any batteries though, so
> it will go crazy, copy corrupt data to the DIMMs on the RAID
> controller, which then will refuse to write it to the disk until the
> power comes up, and then write the bad dat
I couldn't load it on a FAT32 partition on an XP HOME pc. So I loaded
it on the NTSF partition of the same drive.
I don't know why it did & now doesn't work but it could be that you
need to defrag and clear some space.
To change partition types you need to re-format (resetting partitions
will los
Cheaper solution is to get a second hard drive an put it in your
computer as a slave
yes you could xcopy your drive to some backup device then repartition
and plop it back - that would take alot of work and involves
DiskCopy/Ghost like software and has great risk. (Run Defrag first -
Plus you
Unless I missed something, I think you can select on a fresh install
but not after. I doubt even an image could be switched but I could be
wrong, I am too often.
Troy
---(end of broadcast)---
TIP 3: Have you checked our extensive FAQ?
On 27 Oct 2005, at 14:57, Tom Lane wrote:
Alex Stapleton <[EMAIL PROTECTED]> writes:
suspicion is that if the power failure isn't a particularly fast one,
(e.g. you overloaded a fuse somewhere, fuses are insanely slow to
fail compared to alternatives like MCBs) then your RAID card's RAM
will
In article <[EMAIL PROTECTED]>,
Welty, Richard <[EMAIL PROTECTED]> wrote:
>crappy disk drives and bad windows file systems, nothing more.
Could even be crappy memory.
--
http://yosemitecampsites.com/
---(end of broadcast)---
TIP 4: Have you search
Alex Stapleton <[EMAIL PROTECTED]> writes:
> suspicion is that if the power failure isn't a particularly fast one,
> (e.g. you overloaded a fuse somewhere, fuses are insanely slow to
> fail compared to alternatives like MCBs) then your RAID card's RAM
> will get corrupted as the voltage drops
>> If I turn power off by breaking power cord when Postgres server is busy,
>> is it possible that
>> after that SELECT * FROM anytable does not work ?
>
> It is always *possible*, but if your system isn't caching writes then it
> is *very very* unlikely. The tricky bit is that a lot of IDE drive
Andrus wrote:
If data on your disk gets corrupted then NOTHING can guarantee to recover
your database - not PG, not Firebird, not Oracle.
Richard,
thank you for reply. I ask my questing more presicely:
I have configuration like in my previous message. Hardware (IDE drive,
computer) and soft
On Thu, Oct 27, 2005 at 02:54:50PM +0300, Andrus wrote:
> I have configuration like in my previous message. Hardware (IDE drive,
> computer) and software (Windows XP) works according to vendor
> specifications.
>
> If I turn power off by breaking power cord when Postgres server is busy, is
> it
> If data on your disk gets corrupted then NOTHING can guarantee to recover
> your database - not PG, not Firebird, not Oracle.
Richard,
thank you for reply. I ask my questing more presicely:
I have configuration like in my previous message. Hardware (IDE drive,
computer) and software (Windows
Andrus wrote:
My problem: Sometimes I need also to run desktop (server and client in same
desktop computer) applications with Postgres.
Desktop computer have this config. It is not possible to force users to buy
SCSI drives nor upses for each desktop computer.
Can Firebird or SQLLite automatica
>> Why the corruption occurs ?
>
> Most likely because the IDE was caching the information. IDE drives
> sometimes lie about having caching turned on or off.
>
>> Will NTFS file system prevent all corruptions ?
>
> No.
Joshua,
thank you. Please re-confirm. In the configuration
1. Windows XP
2.
On 26 Oct 2005, at 19:43, snacktime wrote:
I remember a few months back when someone hit the emergency power
switch to the whole floor where we host at Internap. Subsequently
the backup power system had a cascading failure. Livejournal, who
also hosts there, was up all night and into t
Andrus wrote:
> Will NTFS file system prevent all corruptions ? If yes, how to convert FAT32
> to NTFS without losing data in drive ?
iirc (i'm not on windows currently, google for the exact syntax),
at the dos prompt, type:
convert /fs:ntfs C:
and it will schedule a conversion after the next
Just to add another story...
I've been running PostgreSQL on Linux since the 6.x days and back then I was
almost always on IDE drives with an EXT2 filesystem. To date, the worse class
of
experiences I've had was going through the fs recovery steps for EXT2. In
those cases I never lost data in t
snacktime wrote:
>
> I remember a few months back when someone hit the emergency power switch
> to the whole floor where we host at Internap. Subsequently the backup
> power system had a cascading failure. Livejournal, who also hosts
> there, was up all night and into the next day restoring thei
Wes Williams writes:
>Even with a primary UPS on the *entire PostgreSQL server* does one still
>need, or even still recommend, a battery-backed cache on the RAID controller
>card? [ref SCSI 320, of course]
>If so, I'd be interest in knowing briefly why.
it can be a lot faster.
if the raid contr
On Wed, 2005-10-26 at 13:38, Wes Williams wrote:
> Even with a primary UPS on the *entire PostgreSQL server* does one still
> need, or even still recommend, a battery-backed cache on the RAID controller
> card? [ref SCSI 320, of course]
>
> If so, I'd be interest in knowing briefly why.
I'll tel
"Wes Williams" <[EMAIL PROTECTED]> writes:
> Even with a primary UPS on the *entire PostgreSQL server* does one still
> need, or even still recommend, a battery-backed cache on the RAID controller
> card? [ref SCSI 320, of course]
>
> If so, I'd be interest in knowing briefly why.
UPSs can fail
I remember a few months back when someone hit the emergency power
switch to the whole floor where we host at Internap. Subsequently
the backup power system had a cascading failure. Livejournal, who
also hosts there, was up all night and into the next day restoring
their mysql databases after a b
Even with a primary UPS on the *entire PostgreSQL server* does one still
need, or even still recommend, a battery-backed cache on the RAID controller
card? [ref SCSI 320, of course]
If so, I'd be interest in knowing briefly why.
Thanks.
-Original Message-
===snip===
...
every server I'
On Wed, 2005-10-26 at 11:14, Gregory Youngblood wrote:
> Talking with various people that ran postgres at different times, one
> thing they always come back with in why mysql is so much better:
> postgresql corrupts too easily and you lose your data.
>
> Personally, I've not seen corruption in pos
TED]
> [mailto:[EMAIL PROTECTED] Behalf Of Joshua D.
> Drake
> Sent: Wednesday, October 26, 2005 1:10 PM
> To: Andrus
> Cc: pgsql-general@postgresql.org
> Subject: Re: [GENERAL] Why database is corrupted after re-booting
>
>
> On Wed, 2005-10-26 at 19:14 +0300, Andrus wrote:
Behalf Of Joshua D. Drake
Sent: Wednesday, October 26, 2005 1:10 PM
To: Andrus
Cc: pgsql-general@postgresql.org
Subject: Re: [GENERAL] Why database is corrupted after re-booting
On Wed, 2005-10-26 at 19:14 +0300, Andrus wrote:
> > To change partition types you need to re-format (resetting par
>
> AFAICS mysql will have exactly the same problems. So will oracle or
> any other DB. Oracle may have a better looking track record, but
> that's probably because people don't try to run it on cheap junk PCs.
Can I quote this?
>
> regards, tom lane
>
> --
On Wed, 2005-10-26 at 19:14 +0300, Andrus wrote:
> > To change partition types you need to re-format (resetting partitions
> > will lose data structure - reformat required).
>
> Troy,
>
> Whole my IDE drive is 20 GB FAT32 C: drive booting XP
> I have a lot of data in this drive so it is not possi
Gregory Youngblood <[EMAIL PROTECTED]> writes:
> Is corruption a problem? I don't think so - but I want to make sure I
> haven't had my head in the sand for a while. :) I realize this instance
> appears to be on Windows, which is relatively new as a native Windows
> program. I'm really after the an
Gregory Youngblood wrote:
>Is corruption a problem? I don't think so - but I want to make sure I haven't
>had my
>head in the sand for a while. :) I realize this instance appears to be on
>Windows,
>which is relatively new as a native Windows program. I'm really after the
>answer on
>more m
On Wed, 2005-10-26 at 18:27 +0300, Andrus wrote:
> Yesterday computer running Postgres re-boots suddenly. After that,
>
> select * from firma1.klient
>
> returns
>
> ERROR: invalid page header in block 739 of relation "klient"
>
> I have Quantum Fireball IDE drive, write caching is turned OFF
On Wed, 2005-10-26 at 10:27, Andrus wrote:
> Yesterday computer running Postgres re-boots suddenly. After that,
>
> select * from firma1.klient
>
> returns
>
> ERROR: invalid page header in block 739 of relation "klient"
>
> I have Quantum Fireball IDE drive, write caching is turned OFF.
> I
Talking with various people that ran postgres at different times, one thing they always come back with in why mysql is so much better: postgresql corrupts too easily and you lose your data.
Personally, I've not seen corruption in postgres since 5.x or 6.x versions from several years ago. And,
> To change partition types you need to re-format (resetting partitions
> will lose data structure - reformat required).
Troy,
Whole my IDE drive is 20 GB FAT32 C: drive booting XP
I have a lot of data in this drive so it is not possible to re-format. Also
I do'nt want to create two logical disk
Yesterday computer running Postgres re-boots suddenly. After that,
select * from firma1.klient
returns
ERROR: invalid page header in block 739 of relation "klient"
I have Quantum Fireball IDE drive, write caching is turned OFF.
I have Windows XP with FAT32 file system.
I'm using PostgreSQL 8
50 matches
Mail list logo
