Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without - Mailing list pgsql-hackers

From Fujii Masao
Subject Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
Date
Msg-id 3f0b79eb1002012040r777313bcv4d3b13c72cecc0d8@mail.gmail.com
Whole thread Raw
In response to Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without  (Heikki Linnakangas <heikki.linnakangas@enterprisedb.com>)
Responses Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without
List pgsql-hackers
On Mon, Feb 1, 2010 at 7:40 PM, Heikki Linnakangas
<heikki.linnakangas@enterprisedb.com> wrote:
> So you get those messages when the table is *not* a temporary table. I
> can see now what Fujii was trying to say. His patch seems Ok, though
> perhaps it would be better to move the responsibility of calling
> XLogReportUnloggedStatement() to the callers of heap_sync(). When I put
> it in heap_sync(), I didn't take into account that it's sometimes called
> just to flush buffers from buffer cache, not to fsync() non-WAL-logged
> operations.

As you said, I moved the responsibility of calling XLogReportUnloggedStatement()
to the callers of heap_sync(). Here is the patch.

Regards,

--
Fujii Masao
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

Attachment

pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: plpython3
Next
From: KaiGai Kohei
Date:
Subject: Re: Largeobject Access Controls (r2460)