| From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
|---|---|
| To: | Rob Wultsch <wultsch(at)gmail(dot)com> |
| Cc: | Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: making an unlogged table logged |
| Date: | 2011-01-05 04:13:38 |
| Message-ID: | 1294200818.6949.50.camel@jd-desktop |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > --
> > Robert Haas
> > EnterpriseDB: http://www.enterprisedb.com
> > The Enterprise PostgreSQL Company
>
> A couple thoughts:
> 1. Could the making a table logged be a non-exclusive lock if the
> ALTER is allowed to take a full checkpoint?
If possible, that would certainly be better. If the bgwriter is doing
what it is supposed to, it would be relatively painless.
> 2. Unlogged to logged has giant use case.
Agreed.
JD
--
PostgreSQL.org Major Contributor
Command Prompt, Inc: http://www.commandprompt.com/ - 509.416.6579
Consulting, Training, Support, Custom Development, Engineering
http://twitter.com/cmdpromptinc | http://identi.ca/commandprompt
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Shigeru HANADA | 2011-01-05 05:52:07 | Re: SQL/MED - core functionality |
| Previous Message | Shigeru HANADA | 2011-01-05 03:58:36 | Re: SQL/MED - core functionality |