| From: | Josh Berkus <josh(at)agliodbs(dot)com> |
|---|---|
| To: | "A(dot)M(dot)" <agentm(at)themactionfaction(dot)com> |
| Cc: | pgsql-hackers Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: making an unlogged table logged |
| Date: | 2011-01-05 20:58:24 |
| Message-ID: | 4D24DB70.3040202@agliodbs.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Hm- if the unlogged tables are being used as HTTP transient state storage, it would be handy to have that (admittedly non-essential) data on the standby when it becomes master, even if there are no guarantees surrounding the data beyond "it looked like this at some point". Since the tables are not writing WAL, would it be possible to allow for writing to unlogged tables on the standby to allow for out-of-band syncing? Otherwise, it seems the only alternative is to push changes to a separate database on the standby machine and then suck the data in when it becomes master.
It would be useful (this would allow per-standby buffer tables, for that
matter), but it would also be tremendously difficult. Seems worthy of a
TODO, though.
--
-- Josh Berkus
PostgreSQL Experts Inc.
http://www.pgexperts.com
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Dimitri Fontaine | 2011-01-05 21:25:22 | Re: can shared cache be swapped to disk? |
| Previous Message | Jesper Krogh | 2011-01-05 20:22:54 | Re: crash-safe visibility map, take three |