| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Andres Freund <andres(at)2ndquadrant(dot)com> |
| Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, "maxim(dot)boguk" <maxim(dot)boguk(at)gmail(dot)com>, Pg Bugs <pgsql-bugs(at)postgresql(dot)org> |
| Subject: | Re: BUG #10675: alter database set tablespace and unlogged table |
| Date: | 2014-07-02 15:38:51 |
| Message-ID: | 4065.1404315531@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs |
Andres Freund <andres(at)2ndquadrant(dot)com> writes:
> I think one reason for the separate flag is that the checkpoint
> performed by pg_start_backup/pg_basebackup shouldn't just become more
> expensive because unlogged tables are needlessly flushed to disk. After
> all, unlogged tables are used because normal tables have a too high
> overhead in that scenario.
AFAIK, the "overhead" that unlogged tables are trying to avoid is WAL
I/O. Nobody has argued (until this thread) that we are worried about
whether checkpoints write them.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Robert Haas | 2014-07-02 15:46:11 | Re: BUG #10675: alter database set tablespace and unlogged table |
| Previous Message | Matthias Raffelsieper | 2014-07-02 14:06:27 | Re: BUG #10836: Rule with RETURNING claims incorrect type |