Timeline for PostgreSQL: Log statements which do sequential scans
Current License: CC BY-SA 3.0
12 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 3, 2018 at 7:10 | vote | accept | guettli | ||
| S May 2, 2018 at 16:59 | history | bounty ended | CommunityBot | ||
| S May 2, 2018 at 16:59 | history | notice removed | CommunityBot | ||
| Apr 30, 2018 at 19:52 | comment | added | Lennart - Slava Ukraini | just curious, pg_stat_all_tables appears to be a view. Is the view definition accessible from the catalog? I don't have a running psql installation to play with, I tried db-fiddle.com but could not find anything | |
| Apr 25, 2018 at 7:16 | history | tweeted | twitter.com/StackDBAs/status/989040436470743040 | ||
| S Apr 24, 2018 at 15:38 | history | bounty started | guettli | ||
| S Apr 24, 2018 at 15:38 | history | notice added | guettli | Draw attention | |
| Apr 5, 2018 at 19:48 | answer | added | user1822 | timeline score: 3 | |
| Apr 5, 2018 at 10:09 | comment | added | guettli | @a_horse_with_no_name I see no need for storing the execution plan. A warning which gets emitted at the moment of the seq scan is enough for me. | |
| Apr 5, 2018 at 9:13 | comment | added | user1822 | I don't think there is a way to get that information as Postgres does not store the execution plans (e.g. like Oracle does) | |
| Apr 5, 2018 at 9:10 | history | edited | user1822 | CC BY-SA 3.0 |
Postgres is doing a sequential scan, it's not scanning a sequence
|
| Apr 5, 2018 at 9:05 | history | asked | guettli | CC BY-SA 3.0 |