Timeline for Performance impact of updating target columns with same values ON CONFLICT
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 7, 2020 at 22:25 | history | edited | CommunityBot |
added [postgresql-performance] to 571 questions - Shog9 (Id=1924)
|
|
| Nov 24, 2018 at 8:38 | comment | added | GeekJock | @a_horse_with_no_name See a1ex07's response below. In Postgres, updates insert new table and index tuples so it looks like it doesn't matter whether or not the non-indexed column is updated. The exception to this is when using HOT updates – in that case, there is a performance penalty if changing the value of an indexed column. | |
| Nov 24, 2018 at 3:49 | vote | accept | GeekJock | ||
| Nov 23, 2018 at 18:42 | answer | added | a1ex07 | timeline score: 3 | |
| Nov 23, 2018 at 7:47 | comment | added | user1822 | There is no optimization in Postgres (or most other DBMS) that would prevent overwriting a column value with the exact same value. Updating indexed columns is more expensive than updating non-indexed columns. So query #2 will be the better choice. | |
| Nov 22, 2018 at 19:32 | history | edited | GeekJock | CC BY-SA 4.0 |
added 7 characters in body
|
| Nov 22, 2018 at 19:18 | history | edited | GeekJock | CC BY-SA 4.0 |
added 526 characters in body
|
| Nov 22, 2018 at 19:10 | review | First posts | |||
| Nov 22, 2018 at 20:56 | |||||
| Nov 22, 2018 at 19:09 | history | asked | GeekJock | CC BY-SA 4.0 |