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

From Robert Haas
Subject Re: COPY FREEZE and PD_ALL_VISIBLE
Date
Msg-id CA+Tgmobg152avMQLXQQ7dWbhFK6sgyfuff_cNzz8WoKaZJqy2g@mail.gmail.com
Whole thread Raw
In response to COPY FREEZE and PD_ALL_VISIBLE  (Jeff Janes <jeff.janes@gmail.com>)
Responses Re: COPY FREEZE and PD_ALL_VISIBLE  (Jeff Janes <jeff.janes@gmail.com>)
List pgsql-hackers
On Sun, Oct 18, 2015 at 5:23 PM, 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.

*facepalm*

I don't know how hard that is to implement, but +1 for trying to
figure out a way.

-- 
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: Allow ssl_renegotiation_limit in PG 9.5
Next
From: rajan
Date:
Subject: Re: SuperUser check in pg_stat_statements