| From: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | Josh Berkus <josh(at)agliodbs(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Wiki Page Draft for upcoming release |
| Date: | 2014-03-19 17:37:50 |
| Message-ID: | 20140319173750.GI6899@eldon.alvh.no-ip.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Tom Lane wrote:
> Josh Berkus <josh(at)agliodbs(dot)com> writes:
> > On 03/17/2014 05:49 PM, Josh Berkus wrote:
> >> https://wiki.postgresql.org/wiki/20140320UpdateIssues
>
> > Anyone? We're going public with this in 36 hours, so I'd love for it to
> > actually be correct.
>
> I did a bit more hacking on this page. Could use another look from Alvaro
> and/or Andres, I'm sure.
Edited, mainly to remove mention of FOR NO KEY UPDATE as a possible
cause of the problem. I don't know that this can cause an issue, since
that lock level conflicts with updates.
I wonder about suggesting other versions of ALTER TABLE that can do
heap rewrites.
--
Álvaro Herrera http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2014-03-19 18:02:50 | Re: pg_archivecleanup bug |
| Previous Message | Jeff Janes | 2014-03-19 17:34:36 | effective_cache_size cannot be changed by a reload |