On Mon, Feb 1, 2010 at 7:40 PM, Heikki Linnakangas
<heikki(dot)linnakangas(at)enterprisedb(dot)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

In response to

• Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without at 2010-02-01 10:40:51 from Heikki Linnakangas

Responses

• Re: [COMMITTERS] pgsql: Write a WAL record whenever we perform an operation without at 2010-02-03 10:03:00 from Heikki Linnakangas

pgsql-hackers by date

Next:	From: KaiGai Kohei	Date: 2010-02-02 04:49:52
	Subject: Re: Largeobject Access Controls (r2460)
Previous:	From: Fujii Masao	Date: 2010-02-02 04:33:44
	Subject: Re: PITR - Bug or feature?

pgsql-committers by date

Next:	From: User Itagaki	Date: 2010-02-02 11:08:52
	Subject: pgbulkload - pgbulkload: Read control files in the client program, and
Previous:	From: User Gleu	Date: 2010-02-01 20:53:32
	Subject: pgsnap - pgsnap: Update index.