| From: | Israel Brewster <ijbrewster(at)alaska(dot)edu> |
|---|---|
| To: | Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca> |
| Cc: | "pgsql-general(at)lists(dot)postgresql(dot)org" <pgsql-general(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: UPDATE many records |
| Date: | 2020-01-07 20:58:49 |
| Message-ID: | F9677E36-0B9C-4C5C-9251-568F3CEC1827@alaska.edu |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-general |
> On Jan 7, 2020, at 11:56 AM, Alan Hodgson <ahodgson(at)lists(dot)simkin(dot)ca> wrote:
>
> On Tue, 2020-01-07 at 11:47 -0900, Israel Brewster wrote:
>> One potential issue I just thought of with this approach: disk space.
>> Will I be doubling the amount of space used while both tables exist?
>> If so, that would prevent this from working - I don’t have that much
>> space available at the moment.
>
> The original update you planned would do that, too.
>
> You probably need to just do the update in batches and vacuum the table
> between batches.
>
>
Really? Why? With the update I am only changing data - I’m not adding any additional data, so the total size should stay the same, right? I’m obviously missing something… :-)
---
Israel Brewster
Software Engineer
Alaska Volcano Observatory
Geophysical Institute - UAF
2156 Koyukuk Drive
Fairbanks AK 99775-7320
Work: 907-474-5172
cell: 907-328-9145
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Adrian Klaver | 2020-01-07 21:01:03 | Re: UPDATE many records |
| Previous Message | Alan Hodgson | 2020-01-07 20:56:16 | Re: UPDATE many records |