Re: Why copy_relation_data only use wal when WAL archiving is enabled

From: Heikki Linnakangas <heikki(at)enterprisedb(dot)com>
To: Jacky Leng <lengjianquan(at)163(dot)com>
Cc: pgsql-hackers(at)postgresql(dot)org
Subject: Re: Why copy_relation_data only use wal when WAL archiving is enabled
Date: 2007-10-16 10:51:17
Message-ID: 471497A5.9040907@enterprisedb.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Jacky Leng wrote:
> If I run the database under non-archiving mode, and execute the following
> command:
> alter table t set tablespace tblspc1;
> Isn't it possible that the "new t" cann't be recovered?

No. At the end of copy_relation_data we call smgrimmedsync, which fsyncs
the new relation file.

--
Heikki Linnakangas
EnterpriseDB http://www.enterprisedb.com

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Magnus Hagander 2007-10-16 11:13:16 Re: Windows and locales and UTF-8 (oh my)
Previous Message Magnus Hagander 2007-10-16 10:38:26 Re: pgsql: Add sample text search dictionary templates and parsers, to

Browse pgsql-patches by date

  From Date Subject
Next Message Marko Kreen 2007-10-16 15:29:34 [RFC] extended txid docs
Previous Message Jacky Leng 2007-10-16 10:30:10 Why copy_relation_data only use wal when WAL archiving is enabled