-Original Message-
From: pgsql-general-ow...@postgresql.org
[mailto:pgsql-general-ow...@postgresql.org] On Behalf Of t.dalpo...@gmail.com
Sent: Wednesday, October 19, 2016 11:01 AM
To: Michael Paquier
Cc: Albe Laurenz ; pgsql-general@postgresql.org
Subject: Re: [GENERAL] journaled FS
t.dalpo...@gmail.com wrote:
> I don't mind about performance but I absolutely mind about reliability,
> so I was thinking about the safest setting of linux FS and postgresql I
> can use.
Sure, use journaling then.
I do it all the time.
Yours,
Laurenz Albe
--
Sent via pgsql-general mailing list
So, as for the data content of the WAL file, I see that no more page
will be allocated. I wonder if during a crash, strange things can still
happen at disk level however, in particular in SSD devices; on these
things we have no control, and perhaps journaling helps?
As for the metadata, if durin
On Fri, Oct 14, 2016 at 11:27 PM, Albe Laurenz wrote:
> After a successful commit, the WAL file and its metadata are on disk.
> Moreover, the file metadata won't change (except for the write and access
> timestamps) because WAL files are created with their full size and never
> extended, so no WAL
t.dalpo...@gmail.com wrote:
> two question related to the WAL.
>
> 1) I read in the doc that journaled FS is not important as WAL is
> journaling itself. But who garantees that the WAL is written correctly?
> I know that it's sequential and a partial update of WAL can be discarded
> after a res
Hi,
two question related to the WAL.
1) I read in the doc that journaled FS is not important as WAL is
journaling itself. But who garantees that the WAL is written correctly?
I know that it's sequential and a partial update of WAL can be discarded
after a restart. But am I sure that without
