| From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: making an unlogged table logged |
| Date: | 2011-01-05 19:37:34 |
| Message-ID: | AANLkTikCmH4BdEB3AkPgw3x08mGB7Vd2TPxg47Cqixix@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Wed, Jan 5, 2011 at 2:36 PM, Simon Riggs <simon(at)2ndquadrant(dot)com> wrote:
> The lock strength selected on the master doesn't need to be the same as
> the lock strength on the standby. You could quite easily generate AEL
> lock records to send to standby, without actually taking that lock level
> on the master.
True.
> Question: what does an unlogged table look like on the standby? Are they
> visible at all, does it throw an error, or do they just look empty. We
> probably need some docs in the HS section to explain that. I hope the
> answer isn't "look empty" since that is effectively data loss for people
> spreading queries across multiple nodes.
Error.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
| From | Date | Subject | |
|---|---|---|---|
| Next Message | A.M. | 2011-01-05 19:55:53 | Re: making an unlogged table logged |
| Previous Message | Dimitri Fontaine | 2011-01-05 19:36:24 | Re: Upgrading Extension, version numbers |