| From: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
|---|---|
| To: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | COPY FREEZE and PD_ALL_VISIBLE |
| Date: | 2015-10-18 21:23:24 |
| Message-ID: | CAMkU=1w3osJJ2FneELhhNRLxfZitDgp9FPHee08NT2FQFmz_pQ@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
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.
Cheers,
Jeff
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andres Freund | 2015-10-18 22:36:52 | Re: checkpointer continuous flushing |
| Previous Message | Shay Rojansky | 2015-10-18 20:56:12 | Re: Allow ssl_renegotiation_limit in PG 9.5 |