| From: | Hannu Krosing <hannu(at)2ndQuadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, Fabrízio Mello <fabriziomello(at)gmail(dot)com>, Pgsql Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: GSoC proposal - "make an unlogged table logged" |
| Date: | 2014-03-03 17:40:16 |
| Message-ID: | 5314BE80.3000209@2ndQuadrant.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 03/03/2014 05:22 PM, Tom Lane wrote:
> Stephen Frost <sfrost(at)snowman(dot)net> writes:
...
>> ISTR the discussion going something along the lines of "we'd have to WAL
>> log the entire table to do that, and if we have to do that, what's the
>> point?".
> IIRC, the reason you'd have to do that is to make the table contents
> appear on slave servers. If you don't consider replication then it might
> seem easier.
So switch on logging and then perform CLUSTER/VACUUM FULL ?
Should this work, or is something extra needed ?
Cheers
--
Hannu Krosing
PostgreSQL Consultant
Performance, Scalability and High Availability
2ndQuadrant Nordic OÜ
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2014-03-03 17:42:19 | Re: GSoC proposal - "make an unlogged table logged" |
| Previous Message | Tan Tran | 2014-03-03 17:39:32 | Re: [HACKERS] GSoC on WAL-logging hash indexes |