Search Postgresql Archives

Re: Thoughts on how to avoid a massive integer update.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Thoughts on how to avoid a massive integer update.
From: Rob Sargent <robjsargent@xxxxxxxxx>
Date: Fri, 8 May 2020 11:04:57 -0600
Cc: Adrian Klaver <adrian.klaver@xxxxxxxxxxx>, "pgsql-general@xxxxxxxxxxxxxx" <pgsql-general@xxxxxxxxxxxxxx>
In-reply-to: <0F5992D4-9317-4007-9036-202DC89BA0D8@comscore.com>
References: <C7D3EE42-66B9-44AF-83F4-CB7F0F42486E@comscore.com> <129e882d-fe4c-0ce9-1966-acbcbf94c309@aklaver.com> <0F5992D4-9317-4007-9036-202DC89BA0D8@comscore.com>

Could you show an example table relationship?

It’s a simple one-to-many relationship:
*Info_table*
info_table_sid integer

*data_table*
data_table_sid integer,
info_table_id integer references info_table(info_table_sid),

Right, and now you wish to change the values in the referenced table (info_table.info_table_sid) correct?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Follow-Ups:
- Re: Thoughts on how to avoid a massive integer update.
  - From: Fehrle, Brian

References:
- Thoughts on how to avoid a massive integer update.
  - From: Fehrle, Brian
- Re: Thoughts on how to avoid a massive integer update.
  - From: Adrian Klaver
- Re: Thoughts on how to avoid a massive integer update.
  - From: Fehrle, Brian

Prev by Date: Re: Thoughts on how to avoid a massive integer update.
Next by Date: Re: Best way to use trigger to email a report ?
Previous by thread: Re: Thoughts on how to avoid a massive integer update.
Next by thread: Re: Thoughts on how to avoid a massive integer update.
Index(es):
- Date
- Thread

[Index of Archives] [Postgresql Jobs] [Postgresql Admin] [Postgresql Performance] [Linux Clusters] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Postgresql & PHP] [Yosemite]

Powered by Linux