Re: COPY FREEZE and PD_ALL_VISIBLE - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: COPY FREEZE and PD_ALL_VISIBLE
Date
Msg-id CANP8+j+Ewz8JWjV9AyuLZZ2+zqeEp+7nw4nrS5HbTya1VBf4YQ@mail.gmail.com
Whole thread Raw
In response to COPY FREEZE and PD_ALL_VISIBLE  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On 18 October 2015 at 17:23, Jeff Janes <jeff.janes@gmail.com> wrote:
I'm planning on adding a todo item to have COPY FREEZE set PD_ALL_VISIBLE.  Or is there some reason this can't be done?

Since the whole point of COPY FREEZE is to avoid needing to rewrite the entire table, it seems rather perverse that the first time the table is vacuumed, it needs to rewrite the entire table.

That's pretty darn weird. I remember measuring the benefit during testing. I remember Jeff D was talking about removing that flag at that time, so perhaps that's it.

Either way, my bug, my bad, thanks for the report.

--
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: Noah Misch
Date:
Subject: Re: Re: [BUGS] BUG #13611: test_postmaster_connection failed (Windows, listen_addresses = '0.0.0.0' or '::')
Next
From: Simon Riggs
Date:
Subject: Re: COPY FREEZE and PD_ALL_VISIBLE