#1507 closed enhancement (wontfix)
Performance improvement: reduce savepoints in function
Reported by: | strk | Owned by: | strk |
---|---|---|---|
Priority: | medium | Milestone: | PostGIS Fund Me |
Component: | topology | Version: | master |
Keywords: | Cc: |
Description
It's been reported that savepoints/EXCEPTION (subtransactions) are particularly expensive. The topology code make heavy use of them. Switching back may give _a_lot_ of performance benefit.
Quoting from #postgresql:
< andres> (like two orders of magnitude or so) < andres> improving subtxn performance is on the roadmap, but one partial patch was reverted again (incomplete, broken) < andres> It also doesn't scale linearly with multiple subtxn in one txn
... may need a 2.0.1 milestone
Change History (6)
comment:1 by , 13 years ago
comment:3 by , 12 years ago
Milestone: | PostGIS 2.1.0 → PostGIS 2.2.0 |
---|
later. Push back if you think you can get to it by next week.
comment:4 by , 10 years ago
Milestone: | PostGIS 2.2.0 → PostGIS Future |
---|
comment:5 by , 8 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Closing as deprecated now that most topology is done in C rather than plpgsql (I don't think we're using savepoints there).
Note:
See TracTickets
for help on using tickets.
Reference about error trapping being "significantly more expensive": http://www.postgresql.org/docs/8.4/interactive/plpgsql-control-structures.html#PLPGSQL-ERROR-TRAPPING