Timeline for Using PostgreSQL functions instead of joining?
Current License: CC BY-SA 4.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 14, 2018 at 0:28 | comment | added | Erwin Brandstetter | I have turned this into a new question (and answer): dba.stackexchange.com/q/212195/3684 | |
| Jul 13, 2018 at 1:32 | comment | added | Evan Carroll |
I also don't think it is correct to say actually harm performance. I think you can mistakenly mark a function as immutable and get bad results because it'll get inlined when it otherwise wouldn't, but I don't think it'll "harm performance." I would like to see a test-case where IMMUTABLE actually makes performance worse.
|
|
| Jul 13, 2018 at 1:29 | comment | added | Evan Carroll | Yes. You can use a prepared statement outside a function too. I don't see how any of this addresses the question. It's seems entirely tangential to me; but, different strokes for different folks. | |
| Jul 1, 2018 at 12:25 | history | edited | Erwin Brandstetter | CC BY-SA 4.0 |
deleted 1 character in body
|
| Jul 1, 2018 at 2:54 | history | answered | Erwin Brandstetter | CC BY-SA 4.0 |