Re: Thoughts on how to avoid a massive integer update. - Mailing list pgsql-general

From David G. Johnston
Subject Re: Thoughts on how to avoid a massive integer update.
Date
Msg-id CAKFQuwYkvURpOY+pJSX53kEfmx6-xzJpLYdT9Au0Ppf3_Q34Wg@mail.gmail.com
Whole thread Raw
In response to Re: Thoughts on how to avoid a massive integer update.  (Rob Sargent <robjsargent@gmail.com>)
Responses Re: Thoughts on how to avoid a massive integer update.  (Rob Sargent <robjsargent@gmail.com>)
List pgsql-general
On Fri, May 8, 2020 at 1:41 PM Rob Sargent <robjsargent@gmail.com> wrote:
My understanding is the keys in the info_table need to change.  That causes the very expensive update in the update in the data tables. No? 

The keys in the info_table need to change because their contents are no longer legal to be stored (OP has not specified but think using an integer value of someones social security number as a key).  The FK side of the relationship equality has the same illegal data values problem and need to be changed too.

David J.

pgsql-general by date:

Previous
From: Support
Date:
Subject: Re: pg_basebackup cannot compress to STDOUNT
Next
From: Rob Sargent
Date:
Subject: Re: Thoughts on how to avoid a massive integer update.