Timeline for PostgreSQL: How to list all stored functions that access specific table
Current License: CC BY-SA 4.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Feb 21, 2019 at 0:48 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
update pg 11 & links
|
| Aug 7, 2018 at 0:47 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
Explain, add disclaimers and links, simplify query
|
| Jul 5, 2014 at 17:56 | history | edited | Erwin Brandstetter | CC BY-SA 3.0 |
typo
|
| Jul 25, 2013 at 15:11 | history | migrated | from stackoverflow.com (revisions) | ||
| Jul 25, 2013 at 11:16 | comment | added | Sergii Kudriavtsev | Thanks for the answer! I actually don't use dynamic table name construction anywhere and all table names are lowercase. | |
| Jul 25, 2013 at 11:14 | vote | accept | Sergii Kudriavtsev | ||
| Jul 25, 2013 at 6:12 | comment | added | Craig Ringer |
So long as the operator isn't crazy enough to actually create tables named "MyTable" and MyTable, at least... and honestly, that's a "well, that might be allowed but it isn't smart" move.
|
|
| Jul 25, 2013 at 5:43 | comment | added | Erwin Brandstetter |
@CraigRinger: Yeah, dynamic queries with EXECUTE are almost impossible to cover. But case-folding can be covered with ~* instead of ~ - or any other case-insensitive pattern-matching.
|
|
| Jul 25, 2013 at 5:38 | comment | added | Craig Ringer |
Yep... it's not totally robust, in the sense that it won't find EXECUTE expressions like 'mm_'||name_parameter, and it won't cope correctly with quoted names like "my""table"" or with case-folding, but it'll do most of what most people will want.
|
|
| Jul 25, 2013 at 5:34 | history | answered | Erwin Brandstetter | CC BY-SA 3.0 |