| From: | Tatsuo Ishii <ishii(at)postgresql(dot)org> |
|---|---|
| To: | klaussfreire(at)gmail(dot)com |
| Cc: | sfrost(at)snowman(dot)net, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: Implementing incremental backup |
| Date: | 2013-06-19 22:54:29 |
| Message-ID: | 20130620.075429.92168895872404702.t-ishii@sraoss.co.jp |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
>>> I'm trying to figure out how that's actually different from WAL..? It
>>> sounds like you'd get what you're suggesting with simply increasing the
>>> checkpoint timeout until the WAL stream is something which you can keep
>>> up with. Of course, the downside there is that you'd have to replay
>>> more WAL when recovering.
>>
>> Yeah, at first I thought using WAL was a good idea. However I realized
>> that the problem using WAL is we cannot backup unlogged tables because
>> they are not written to WAL.
>
> How does replication handle that?
>
> Because I doubt that's an issue only with backups.
Unlogged tables are not replicated to streaming replication
standbys. It is clearly stated in the doc.
--
Tatsuo Ishii
SRA OSS, Inc. Japan
English: http://www.sraoss.co.jp/index_en.php
Japanese: http://www.sraoss.co.jp
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2013-06-19 22:56:19 | Re: Implementing incremental backup |
| Previous Message | Jeff Janes | 2013-06-19 22:51:36 | Re: Change authentication error message (patch) |